Skip to main content
Glama

req_set_status

Declare a requirement as pending or implemented; computed verified, stale, or unverified states must come from evidence files, not this status change.

Instructions

Declare a requirement's status: pending or implemented. verified, stale and unverified are computed from evidence and are rejected here - write an evidence file instead.

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>",
      "status": "<status>"
    },
    "name": "req_set_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.1/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 usefully discloses validation behavior — the computed statuses are rejected at this endpoint — but says nothing about permissions, idempotency of re-setting a status, or what the caller gets back on success or rejection.

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 short sentences, front-loaded with the core action and followed by the exclusion rule. No filler and no restatement of the tool name.

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 with no annotations and no output schema, the status-value contract is covered well, but the id parameter and the post-call outcomes are unaddressed. An agent could call it correctly only after guessing the id convention.

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 0%, so the description must compensate. It does document the allowed values for status (pending, implemented) and implies id refers to a requirement, but it never specifies the id's form or where it comes from, leaving half the parameters undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The definition gives a specific verb+resource (declare a requirement's status) and immediately bounds it by enumerating the two writable values, pending and implemented. It also distinguishes this write path from the computed statuses (verified, stale, unverified), so an agent can tell what this tool is and is not responsible for.

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

Usage Guidelines5/5

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

It states when to use it (to set pending or implemented), when not to (the three computed statuses are rejected here), and the alternative route (write an evidence file instead). That is explicit when/when-not/alternative guidance rather than inference.

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