Skip to main content
Glama

req_scope

Restrict a requirement’s staleness checks to specific file globs so only matching source changes mark it stale, not every repository change.

Instructions

Restrict a requirement's staleness to specific file globs. Without scope, any source change in the repo marks it stale; with scope, only changes to matching files do.

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": {
      "id": "<id>",
      "files": "<files>"
    },
    "name": "req_scope"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
filesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it discloses the central behavioral trait (narrowing staleness triggers), which is genuinely useful. It is silent on whether calling it replaces an existing scope or appends to it, what happens with invalid or non-matching globs, and whether it requires any permission on the requirement.

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 sentences, zero filler, with the core action first and the behavioral consequence second. Nothing could be trimmed without losing information.

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 two-parameter mutation tool with no annotations and no output schema, the description covers purpose and effect but leaves replace-vs-merge semantics, failure modes, and return/confirmation behavior unstated. Adequate to select the tool, thin for invoking it confidently.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it does add real meaning: "files" are globs (not literal paths), and the requirement is identified by scope, tying "id" to a requirement. It still doesn't give glob syntax examples or say whether an empty array is legal.

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?

"Restrict a requirement's staleness to specific file globs" names a specific verb and resource and states the effect on staleness detection, so it is distinguishable from req_add / req_set_status siblings. It stops short of a one-line summary of what the tool mutates on the requirement object itself.

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?

The second sentence gives a clear use/not-use contrast: unscoped requirements go stale on any repo change, scoped ones only on matching changes. That tells an agent when the tool is worth calling, though it never names an alternative or says whether this should be applied before or after evidence_scan.

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