Skip to main content
Glama

Skillshop

audit_handoff

Check a task/handoff record against the agent-handoff protocol (paid, metered).

record: {id, owner, state, revision, history[], artifact?, blocker?, delivery?, summary?} Returns ok, errors (protocol breaks), warnings (claims not yet supported by evidence), billing.

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": {
      "record": "<record>"
    },
    "name": "audit_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 load. It does disclose that the call is paid and metered and it names the return categories (ok, errors, warnings, billing), which is valuable. It never states that the operation is read-only with no side effects, what authorization is needed, or what the metering costs, so a mutation-capable reading is not fully ruled out.

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?

The purpose statement is front-loaded in one sentence, followed by the record shape and the return categories. Dense but each element earns its place; the terse brace-list formatting is slightly cryptic but appropriate for a reference definition.

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 the return-value enumeration is a bonus rather than a necessity. The remaining gaps are the substance the agent needs to call this correctly: the rules of the 'agent-handoff protocol' being enforced are never described, and the record fields have no accepted-value semantics, which matters for a nested, free-form object.

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 description coverage is 0% and the schema only declares an untyped object with additionalProperties, so the description is the sole documentation. It enumerates the record fields (id, owner, state, revision, history[], artifact?, blocker?, delivery?, summary?) and marks optionality with '?', which is meaningful compensation, but it does not define allowed values, types, or what the protocol requires of each field.

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 gives a specific verb and resource: 'Check a task/handoff record against the agent-handoff protocol'. The handoff-record scope separates it from the other audit_* siblings, though the description never names those siblings or states the boundary 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 implied by the resource (run this when you have a handoff record to validate), and the '(paid, metered)' note is a useful cost hint for deciding whether to invoke. However, there is no explicit when-to-use/when-not guidance and no mention of alternatives such as audit_status_report.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources