Skip to main content
Glama

analyser_perimetre_pr

Résout les propriétaires des chemins modifiés par un diff et liste les chemins orphelins.

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": {
      "diff": "<diff>",
      "codeowners": "<codeowners>"
    },
    "name": "analyser_perimetre_pr"
  }
}

Input Schema

NameRequiredDescriptionDefault
diffYes
codeownersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

The description discloses the basic computational behavior, but there are no annotations to establish safety or side effects. It also omits ownership matching and precedence behavior, invalid-input handling, and whether an orphan means no matching rule or an unresolvable owner.

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 front-loaded sentence covers both operations without filler or repetition. Its brevity is effective, and the missing technical detail is assessed under the other dimensions rather than constituting structural waste.

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

Completeness2/5

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

For a tool with two required inputs, 0% schema coverage, no annotations, and no output schema, this description is insufficient for fully reliable invocation. The absent input formats, ownership-rule semantics, orphan definition, and result structure are material gaps.

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

Parameters2/5

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

With 0% schema description coverage, the sentence only clarifies that `diff` supplies the changed paths; `codeowners` is not explicitly connected to its parameter or defined as file content versus a path. Neither parameter's expected syntax or encoding is documented.

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 gives specific verbs and resources: resolving owners for paths changed by a diff and listing orphan paths. This clearly conveys the tool's function, although it does not define “orphan” or distinguish the tool from siblings.

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 wording implies use when assessing ownership for paths in a PR or other diff, but it states no prerequisites, exclusions, or conditions for preferring another approach. Usage context is therefore implicit rather than explicitly guided.

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