Skip to main content
Glama

Synapse

Which tests to run

tests_for
Read-onlyIdempotent

The test files that cover the given files (direct importers, same-name tests, and tests one import away), so you run only those instead of the whole suite.

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

Input Schema

NameRequiredDescriptionDefault
pathsYesFiles you changed.
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
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: the exact heuristics used to decide coverage (direct importers, same-name tests, one import away), which tells the agent how inclusive the result is. It stops short of stating known blind spots (dynamic imports, language support) or what happens when no tests match.

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?

A single sentence with zero waste: the output is front-loaded, the parenthetical supplies the disambiguating heuristics, and the trailing clause supplies the motivation. Nothing could be removed without losing information.

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 only two fully documented required parameters, no nested objects, and no output schema, the surface area an agent must understand is small, and the description covers the core question of what comes back. Minor gaps remain around the empty-result case and the limits of the coverage heuristic, but they do not block a correct call.

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%, so both parameters — paths and repository — are fully documented in the schema itself. The description only refers to 'the given files' and adds no format, batching, or repository-resolution detail beyond what the schema already says. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific resource — the test files covering the given files — and defines its scope with concrete heuristics (direct importers, same-name tests, tests one import away). It is clearly a test-selection/coverage tool and does not overlap with siblings like read_code or blast_radius, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

The clause 'so you run only those instead of the whole suite' implies the use case: after changing files, select tests to run. However, it gives no explicit when-to-use vs. when-not guidance and does not point at blast_radius or any sibling for the adjacent question of what else a change affects. Usage is inferable but not spelled out.

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