Skip to main content
Glama

Log the outcome of a delegation

log_outcome

Record reviewed child task outcomes as success, corrected, or failure using delegation IDs or task/provider/model details, enabling tuning of provider and model recommendations.

Instructions

Call after reviewing a child's result. Pass delegationId (from log_delegation) or taskType + providerInstanceId + model. outcome: success (accepted as is), corrected (needed fixes) or failure.

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": {
      "outcome": "<outcome>"
    },
    "name": "log_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoShort note (kept to 200 characters). Avoid secrets.
modelNo
outcomeYes
taskTypeNo
delegationIdNo
providerInstanceIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already disclose the write profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=false). The description adds the useful precondition that a review must happen first, and clarifies the enum meanings, but says nothing about duplicate submissions (notably non-idempotent behavior), failed lookups, or required authorization.

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?

Three tight sentences, front-loaded with the trigger condition, then the identifier options, then the outcome semantics. Telegraphese ('success (accepted as is)') is dense but readable; nothing is wasted.

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?

For a six-parameter mutation tool with low schema coverage and no output schema, the description covers the trigger, both addressing modes, and the enum semantics. The remaining gap is what happens on invalid identifiers or repeated calls, which matters given idempotentHint=false.

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 only 17% (just the note field), so the description must compensate and largely does: it explains that delegationId comes from log_delegation, that taskType + providerInstanceId + model is the alternative composite key, and expands all three outcome enum values. Only the model/providerInstanceId meaning itself is left implicit.

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 states the action precisely: record the outcome of a delegation after reviewing a child's result, distinguishing it from log_delegation which is named as the source of delegationId. It is a clear verb+resource statement, though the verb 'log/record' itself is only implied rather than written out.

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?

Timing guidance is explicit and actionable ('Call after reviewing a child's result'), which tells the agent this is a post-review bookkeeping call rather than an arbitrary write. It also gives the two mutually exclusive ways to identify the target, but offers no when-not guidance or error/edge-case conditions.

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

Deploy Server

Other Tools