Skip to main content
Glama

Synapse

Map of the repository

repo_map
Read-onlyIdempotent

One screen on an unfamiliar repo: main areas with their most used code, entry points, API routes and pages, where tests live, and the stack. Call once instead of exploring folders.

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": {
      "repository": "<repository>"
    },
    "name": "repo_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
repositoryYesPublic GitHub repository as "owner/name" (e.g. "pallets/flask") or its github.com URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful framing that output is a single condensed screen and should be called once rather than repeatedly, but says nothing about behavior on very large repos or any output size limits.

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 tight sentences: the payoff (what you get) comes first, followed by the action guidance. Every clause names a concrete artifact type rather than padding.

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

Completeness4/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 usefully enumerates return contents, and one required parameter plus full annotations means little else is needed. Minor gap: nothing about coverage limits for monorepos or how partial/huge repos are handled.

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

Parameters3/5

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

Schema coverage is 100% and the single `repository` parameter already documents the owner/name or URL format. The description adds no further meaning about the input, so the schema does the work; baseline 3 applies.

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

Purpose4/5

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

Names a specific resource (repository map) and enumerates its contents: main areas with most-used code, entry points, API routes, pages, test locations, and stack. That is concrete enough to distinguish it from read_code/tests_for siblings, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

'Call once instead of exploring folders' supplies both a when-to-use condition (unfamiliar repo) and an implicit when-not (don't drill into folders with other tools). It stops short of naming which sibling to use for follow-up depth.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources