Skip to main content
Glama

requirements_check

Read-onlyIdempotent

Transforms workload briefs into explicit requirements, gaps, and research questions without inferring SLAs or budgets.

Instructions

Turn a workload brief into explicit requirements, gaps and research questions. No inferred SLA or budget.

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": {
      "workload": "<workload>"
    },
    "name": "requirements_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
workloadYes
constraintsNo
requirementsNo

Output Schema

NameRequiredDescriptionDefault
kindNo
sourcesNo
workloadNo
nextToolsNo
validatedNo
limitationNo
constraintsNo
requirementsNo
decisionsToClarifyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedInput schema / required
      Previous value: -[
      -  "workload",
      -  "requirements",
      -  "constraints"
      -]New value: +[
      +  "workload"
      +]
  2. First observedv0.4.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety profile is fully covered. The description adds one genuine behavioral boundary — it will not fabricate SLAs or budget figures, so the agent knows those must come from elsewhere. It says nothing about output shape or depth, but an output schema exists to carry that.

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?

Two short, front-loaded sentences with no filler; the deliverable list comes first and the scope boundary second. The boundary sentence is terse to the point of being slightly cryptic, but nothing is wasted.

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?

An output schema exists, so return values need no explanation, and the tool itself is structurally simple (three flat string params). The remaining gap is the constraints-vs-requirements ambiguity, which is the one thing an agent must resolve to call this correctly and which the description does not address.

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?

Schema description coverage is 0%, so the description carries the full burden, and it only partially does: 'workload brief' maps loosely to the required 'workload' param. The distinction between the optional 'constraints' and 'requirements' arrays is left entirely unexplained — an agent cannot tell whether pre-supplied requirements are inputs to reconcile or items to be re-derived.

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 a specific verb ('Turn a workload brief into') and enumerates the outputs: explicit requirements, gaps, and research questions. This is clearly distinct from planning-oriented siblings like implementation_plan or capacity_plan, though it never names a sibling to sharpen the boundary.

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?

Usage is only implied: an agent can infer this is the entry point when handed a raw workload brief, before planning or sizing. There is no explicit when-to-use, no when-not-to-use, and no routing to alternatives. The 'No inferred SLA or budget' line constrains output behavior rather than tool selection.

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