Overmind Agent

Start with list_projects and choose the intended accessible project. For an account connection, pass its project_id on every project tool and resource URI query; follow returned links. Project API keys retain their narrower access.

Turn the Agent surface into an evidence-based account of the project's capabilities, their contracts and the next improvement to make. The agent is the project; capabilities are its nodes, not separate agents.

Establish the map

Use the configured Overmind MCP connection. Read overmind://project/current?project_id=ID for project identity and repository provenance. A missing repository snapshot means the scanned revision is unknown; last_synced_at is not the scan time. Live traces can come from another revision.

Resolve a supplied capability through overmind://capabilities/{capability}. For project-wide orientation, get_instrumentation_plan without a capability returns registered placements and any required local action. Use returned identities; there is no list_capabilities tool. Placements and observed executions are evidence about the map, not proof of complete coverage.

Inspect the capability's status, task context, dataset, eval set, benchmark and live model. A leftover capability is an absent scan result, not a deletion request. MCP cannot create capability cards by scanning a repository.

Connect contracts to evidence

When prompts are supported, use investigate-capability with the resolved capability. Otherwise combine inspect_capability_health and query_failures as needed. Follow relevant trace resource links.

The capability resource lists the eval_matrix rows that score it and the Default set's eval_preload counts. Spans without a capability id indicate a mapping gap; low scoring coverage means spans arrive without evidence the matrix can judge. Missing scores do not demonstrate success.

Choose the next action from the evidence: refresh the repository map, instrument an uncovered entry point, prepare data, repair evaluation coverage or investigate a measured failure. Do not automatically start those mutations during a map review.

Changes and handoffs

Repository discovery runs locally through the installed Overmind setup workflow and overmind sync; MCP cannot inspect an arbitrary Git provider or edit files. If local tooling is unavailable, report that handoff and retain the current map.

benchmark_model selects the incumbent for future comparisons; active_model controls live serving. Preserve both during a map review. Use their respective mutation tools only for the user's requested selection.

Return the capability identities, observed coverage, provenance limitations and the next useful action. For a visual view, open the project's console_url; for one capability use capabilities/{id}, preserving its base and projectId.