mcp: reading a repo's description/topics drops to madt_api_call; add a typed read #723

Open
opened 2026-10-05 15:08:13 +00:00 by hexajon · 0 comments
Owner

Reading a single repo's description and topics has no obvious typed madt_* path, so I reached for the raw forge API twice: GET /repos/{owner}/{repo} for the description, and GET /repos/{owner}/{repo}/topics for the topics. Dropping to the raw API for a routine read is a smell: it is unbounded and bypasses the typed surface.

Ask

  • A typed read for one repo's current metadata values (description, topics, website) - for example madt_repos action="get", returning the same fields that madt_repos check_metadata already audits in aggregate.
  • Failing that, have madt_api_call emit a steer toward the typed tool when the endpoint has a typed equivalent, so the caller is nudged off the raw API.

Context

madt_repos check_metadata reports repos that are MISSING metadata in aggregate, but there is no obvious per-repo read of the current values. That gap is what sent me to the raw API.

Reading a single repo's description and topics has no obvious typed madt_* path, so I reached for the raw forge API twice: GET /repos/{owner}/{repo} for the description, and GET /repos/{owner}/{repo}/topics for the topics. Dropping to the raw API for a routine read is a smell: it is unbounded and bypasses the typed surface. ## Ask - A typed read for one repo's current metadata values (description, topics, website) - for example madt_repos action="get", returning the same fields that madt_repos check_metadata already audits in aggregate. - Failing that, have madt_api_call emit a steer toward the typed tool when the endpoint has a typed equivalent, so the caller is nudged off the raw API. ## Context madt_repos check_metadata reports repos that are MISSING metadata in aggregate, but there is no obvious per-repo read of the current values. That gap is what sent me to the raw API.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sixfold-space/madtea#723
No description provided.