Skip to main content
Glama

Validate a structured swarm task result

swarm_structured_result
Read-only

Recover the stored JSON Schema and domainRule contract for a cb_* or sess_* task, then validate its output.

Instructions

Recover the stored JSON Schema + domainRule contract for a cb_* or sess_* task and validate its output.

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": {
      "taskId": "<taskId>"
    },
    "name": "swarm_structured_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine context beyond that: it discloses that a stored contract is recovered and that output is validated, which tells the agent this is retrieval-plus-check rather than a plain fetch. It omits what happens on validation failure or what the response looks like, which limits it to a 3.

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?

A single front-loaded sentence with no filler; every clause (recover, validate, task prefixes) carries information. It is efficient but so compressed that it reads slightly dense for a tool performing two distinct steps.

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

Completeness4/5

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

There is no output schema, so the description should clarify what validation yields, and it does at a high level ('validate its output') while falling short on result shape or failure signaling. For a single-parameter read-only tool with annotations covering safety, this is largely sufficient but not exhaustive.

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?

With one parameter at 0% schema description coverage, the description must carry the load, and it does explain that taskId identifies a cb_* or sess_* task whose contract is stored. However, it omits the qd_* prefix that the schema pattern explicitly permits, leaving a small mismatch, and adds no guidance on identifier sourcing.

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 pairs specific verbs ('Recover', 'validate') with a specific resource ('stored JSON Schema + domainRule contract') and an output target, which is far more than a restatement of the title. It hints at differentiation from plain result-fetching siblings like swarm_result by emphasizing contract recovery plus validation, though it never names an alternative explicitly.

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: the agent learns this applies to 'cb_* or sess_*' tasks and is about validating structured output, but there is no statement of when to prefer this over swarm_result or zcode_structured_result, nor any prerequisite or when-not guidance. The task-prefix scoping is the only real usage signal.

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