Skip to main content
Glama

Synapse

Why is this code like this?

why
Read-onlyIdempotent

Reasons behind a file or line: decisions from PRs, reviews and reverts, the commit that last changed the line (with its message), the function there and who knows the code. Use before changing or deleting code that looks odd.

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

Input Schema

NameRequiredDescriptionDefault
lineNoOptional line number.
pathYesRepo-relative file path.
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.9/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real value by disclosing the sources consulted (PRs, reviews, reverts, blame) and what is returned, which tells an agent this is a research call with no side effects on the repository.

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?

Two sentences, no filler, with the payload of sources front-loaded and the usage trigger placed at the end. The colon-list is dense but each item is informative rather than decorative.

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 carries the burden of explaining what comes back, and it does so by listing the evidence categories (decisions, blame commit, function, ownership). Only the shape of the response and any cost/latency expectations are left implicit.

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 description coverage is 100%, so path, line, and repository are already documented with format examples. The description only implies the file-vs-line distinction ('a file or line'), adding little beyond the schema, which puts it at the baseline.

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?

The description enumerates concretely what the tool surfaces: PR/review/revert decisions, the last-changing commit with its message, the enclosing function, and code ownership. That is far more specific than a restatement of the name, though it is framed as a noun phrase ('reasons behind') rather than a verb and never names a sibling to contrast with.

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?

'Use before changing or deleting code that looks odd' gives a clear, actionable trigger condition rather than a vague suggestion. It stops short of naming alternatives (e.g., read_code or blast_radius) or stating when the tool is unnecessary, so it is strong but not exhaustive.

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