Skip to main content
Glama

repo_context

Read-onlyIdempotent

Retrieve token-budgeted repository context for a coding task, including file paths, content digests, and source-commit evidence to ground agent responses.

Instructions

Retrieve budgeted repository context with path, digest, and source-commit evidence.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task": "<task>"
    },
    "name": "repo_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYes
token_budgetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.6

TDQS

C2.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description does add marginally useful behavior context by framing the output as 'budgeted' and as carrying path/digest/source-commit 'evidence', implying provenance-tagged results. It says nothing, though, about what happens when the budget is exhausted or how truncation is signaled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler or redundancy. Its terseness is efficient, though the brevity is part of why the definition under-specifies rather than a virtue in itself.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description's mention of returned evidence fields (path, digest, source-commit) is welcome, but it leaves the required 'task' input unexplained and offers no guidance about which sibling tool to choose. For a retrieval entry point with an undocumented required parameter, more is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden of explaining two parameters, and it fails on the more important one: the required 'task' parameter is never mentioned or characterized, leaving its expected granularity entirely opaque. 'Budgeted' only loosely gestures at token_budget and gives no guidance on sensible values or default behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Retrieve') and resource ('repository context') and names what comes back (path, digest, source-commit evidence). However, 'repository context' is an amorphous object and the definition never distinguishes it from the many sibling retrieval tools (repo_search, repo_architecture, repo_explain, repo_graph). An agent cannot tell from this sentence which one to reach for.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: no statement of the situation this tool fits, no exclusion of the alternatives in the sibling set, and no note on when a larger or smaller budget is appropriate. The only contextual hook is the word 'budgeted', which implies scope but does not route the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.