Skip to main content
Glama
token-context-mcp

token-context-mcp

Registered repositories

list_repositories
Read-onlyIdempotent

Lists registered repository IDs and budget profiles so coding agents can choose a valid target before calling repository tools.

Instructions

List registered repo_ids and budget_profiles (empty list if none; roots hidden). Call first before any repo tool; call get_index_status next to verify snapshot freshness.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_repositories"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the tool call fails (either a structured {code, message, details} object or a diagnostic string).
repo_idsNoSorted list of registered repo_id values (empty if none registered).
truncatedNoTrue if repo_ids were truncated to stay under max_result_tokens.
schema_versionNoEnvelope schema version ('1.0').
budget_profilesNoConfigured retrieval budget profiles ('locate', 'orient', 'impact', 'read').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.8
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "budget_profiles": {
      +      "additionalProperties": true,
      +      "description": "Configured retrieval budget profiles ('locate', 'orient', 'impact', 'read').",
      +      "type": "object"
      +    },
      +    "error": {
      +      "additionalProperties": true,
      +      "description": "Present when the tool call fails (either a structured {code, message, details} object or a diagnostic string).",
      +      "properties": {
      +        "code": {
      +          "description": "Machine-readable error code.",
      +          "type": "string"
      +        },
      +        "details": {
      +          "description": "Optional structured metadata for the error.",
      +          "type": "object"
      +        },
      +        "message": {
      +          "description": "Human-readable error explanation.",
      +          "type": "string"
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "string"
      +      ]
      +    },
      +    "repo_ids": {
      +      "description": "Sorted list of registered repo_id values (empty if none registered).",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "schema_version": {
      +      "description": "Envelope schema version ('1.0').",
      +      "type": "string"
      +    },
      +    "truncated": {
      +      "description": "True if repo_ids were truncated to stay under max_result_tokens.",
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds two non-obvious traits the annotations cannot convey: an empty list is the no-results case, and roots are hidden from the result. It stops short of any pagination or size characteristics, but for a zero-argument read that is a minor gap.

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

Conciseness5/5

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

Two sentences, both front-loaded with the actionable clause: what is returned, then how to sequence the call. The parentheticals carry edge-case detail (empty list, hidden roots) without padding, and no sentence is redundant.

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

Completeness5/5

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

An output schema exists, so return values need not be re-explained, and the description still covers the empty-result case and hidden roots, which are the likely sources of agent confusion. For a zero-argument, annotation-covered read tool, nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

The tool takes no parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The description correctly spends its words on output shape and call sequencing instead of inventing parameter semantics.

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

Purpose5/5

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

States a specific verb (list) and resource (registered repo_ids and budget_profiles), and implicitly differentiates itself from get_index_status, which it names as the next step rather than a duplicate. The parenthetical clarifies the result shape, so an agent knows what comes back without opening the output schema.

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

Usage Guidelines5/5

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

Gives explicit ordering guidance: 'Call first before any repo tool' establishes a precondition, and 'call get_index_status next to verify snapshot freshness' names the follow-up tool and its condition. This is when-to-use plus sequencing with a named alternative, leaving little to inference.

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