Skip to main content
Glama

req_list

Lists registered requirements with criteria counts, declared status, and file scope, so developers can review coverage and identify requirements needing verification.

Instructions

List registered requirements, their criteria count, declared status and file scope.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "req_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/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 implies a read-only enumeration and enumerates the fields surfaced per requirement, which is genuinely useful context. It stops short of disclosing ordering, whether all requirements are returned or truncated, or that no scoping filters exist.

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 14-word sentence with the action front-loaded and no filler. Every clause contributes a distinct piece of information about what is returned.

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?

Because there is no output schema, the description is the only source of return-value information, and it lists field names without shape, types, or ordering. For a simple zero-param list tool that is close to adequate, but the returned structure remains under-described.

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?

The tool takes zero parameters, so the schema has nothing to document and there is no parameter meaning for the description to add. Baseline 4 applies; the mention of status and file scope at least tells the agent these are outputs rather than inputs.

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 verb and resource ("List registered requirements") and adds the returned facets (criteria count, declared status, file scope), so an agent knows exactly what this call yields. It does not, however, explicitly contrast itself with siblings such as req_scope or decisions_list, leaving the boundary to be inferred from the names.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no exclusion, and no named alternative. An agent must infer that this is the read-only enumeration path used before req_add or req_set_status; the description never states that condition or mentions that it takes no filters.

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