Skip to main content
Glama

boundary

Read-onlyIdempotent

Read a module's own file, its imports, and its importers before changing it to see what the edit may affect.

Instructions

The files to read before changing a module: the module, what it imports and what imports it.

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": {
      "module": "<module>"
    },
    "name": "boundary"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoList everything instead of stopping at 200 items.
moduleYesModule ID or file path, as printed by other tools (e.g. src/billing/invoice).
files_onlyNoPrint file paths only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds the returned categories (module, imports, importers), but says nothing about the 200-item cutoff behavior surfaced only in the schema, nor about response shape beyond the file set.

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?

One compact sentence, front-loaded with the purpose and followed by a colon list that enumerates scope; nothing is wasted. The phrasing "the module, what it imports and what imports it" is slightly clunky but unambiguous and short.

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

Completeness3/5

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

For a simple read-only, three-parameter tool with full schema coverage and no output schema, the essentials are present. It falls short only in not helping an agent choose between this and the similarly named boundary/dependency siblings, which is the main remaining decision an agent faces.

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 all three parameters (module, all, files_only) are already documented, including the 200-item limit and path format. The description adds no meaning beyond that, which is the correct baseline when the schema carries the load.

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?

States the resource concretely: the module file, its imports, and its importers — an agent can picture exactly what comes back before changing code. It is specific about scope but does not distinguish itself from near-identical siblings such as "boundaries", "deps", or "rdeps".

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 lead clause "the files to read before changing a module" implies the usage context (pre-change reconnaissance), which is real guidance. However, it offers no explicit when-not condition and no routing to alternatives, which matters given siblings named "boundaries", "deps", "rdeps", and "impact" that plausibly overlap.

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