Skip to main content
Glama

Report Post-Handshake Execution Outcome

report_execution_outcome
Idempotent

Submit a single-use HMAC execution_ticket from matchmake_agent_crew to record empirical downstream task completion or failure (+0.05 clean delivery / -0.20 timeout or schema failure on Byte-2 Guarantee grade). Use after invoking a matched agent to close the quality feedback loop.

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": {
      "agent_id": "<agent_id>",
      "execution_ticket": "<execution_ticket>",
      "outcome_success": "<outcome_success>"
    },
    "name": "report_execution_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesTarget agent_id that executed the downstream call.
outcome_successYesTrue if the downstream agent fulfilled its schema contract cleanly; false on timeout, HTTP error, or malformed output.
execution_ticketYesSingle-use HMAC execution_ticket issued by matchmake_agent_crew.
observed_latency_msNoOptional caller-observed round-trip execution latency in milliseconds.

Output Schema

NameRequiredDescriptionDefault
agent_idNoEvaluated target agent_id.
ticket_validYesTrue when the single-use HMAC ticket passed verification and updated telemetry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the scoring consequences (+0.05 clean delivery / -0.20 timeout or schema failure) and that the ticket is single-use, which are the facts an agent most needs before calling. One tension is left unresolved: idempotentHint=true implies safe retry, while 'single-use HMAC execution_ticket' implies a repeat call will fail — the description should reconcile retry behavior.

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 sentences, front-loaded with the action and the required artifact, with no filler. It is dense with jargon ('Byte-2 Guarantee grade') that is not defined, which slightly costs first-read clarity.

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?

With an output schema present, return values need not be explained, and the scoring stakes are covered. However, for a state-mutating, single-use-ticket call the description omits failure/retry semantics and whether an already-reported outcome can be corrected or resubmitted, which an agent needs to avoid a wasted call.

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 100%, so agent_id, outcome_success, execution_ticket, and observed_latency_ms are already fully documented. The description reinforces the ticket's origin but adds no new per-parameter meaning such as valid latency ranges or how outcome_success maps to specific error classes. Baseline 3 is appropriate.

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?

States a concrete verb and resource: submit a single-use execution_ticket to record downstream task completion or failure. It also names where the ticket comes from (matchmake_agent_crew), which cleanly separates this write-back step from the sibling that issues the ticket.

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

Usage Guidelines4/5

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

Explicit timing is given: 'Use after invoking a matched agent to close the quality feedback loop,' plus the constraint that the ticket is single-use. There is no explicit when-not guidance or named alternative for reporting outcomes through another path, so it falls short of the top band.

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.