Skip to main content
Glama

Agentic Keychain

by com.agentickeychain
OverviewDiscussionsAdmin

Report an outcome

report_outcome

Report how a capability worked for you. Stored as AGENT REPORTED; it never changes evidence labels, trust or ranking. Only the listed fields are accepted; no task text is kept. Use when: you ran a capability, or decided not to, and can say whether the task succeeded. Not for: questions about a capability (get_capability, get_benchmark). Input: the capability id and success; add evaluation_id or purchase_ref to link the report, the optional token, tool-call, latency and cost counts, and failure_reason only with success false. Output: whether the report was stored, its label and, for a failed paid capability, the remedy policy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoThe model you run on, e.g. claude-sonnet-5. Savings are reported only for measured models.
successYesWhether the task reached its goal.
cost_usdNoWhat the run cost you in USD.
tokens_inNoInput tokens the run used.
capabilityYesCapability id (ak:publisher:name or ak:publisher:name:x.y.z), ak:// URI or slug.
latency_msNoWall-clock time of the run in milliseconds.
tokens_outNoOutput tokens the run used.
tool_callsNoTool calls the run made.
purchase_refNoThe purchase_ref from unlock_capability, if you bought the capability.
evaluation_idNoThe evaluation_id from evaluate_capability, if you evaluated first.
failure_reasonNoOnly with success false.
used_capabilityNoWhether the capability was used in this run; false reports a run done without it.
baseline_cost_estimate_usdNoWhat one run of this task costs you without the capability, in USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / baseline_cost_estimate_usd / description
      Added value: +"What one run of this task costs you without the capability, in USD."
    • addedInput schema / properties / cost_usd / description
      Added value: +"What the run cost you in USD."
    • addedInput schema / properties / latency_ms / description
      Added value: +"Wall-clock time of the run in milliseconds."
    • addedInput schema / properties / success / description
      Added value: +"Whether the task reached its goal."
    • addedInput schema / properties / tokens_in / description
      Added value: +"Input tokens the run used."
    • addedInput schema / properties / tokens_out / description
      Added value: +"Output tokens the run used."
    • addedInput schema / properties / tool_calls / description
      Added value: +"Tool calls the run made."
    • addedInput schema / properties / used_capability / description
      Added value: +"Whether the capability was used in this run; false reports a run done without it."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so mutation and safety are largely covered; the description goes further by disclosing the storage label (AGENT REPORTED), that the report cannot alter trust/ranking, and that no task text is retained. It does not address the non-idempotent behavior (duplicate submissions) or any auth requirements, which is the remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core semantics, then uses labeled 'Use when / Not for / Input / Output' segments. Every sentence carries information; there is no filler or repetition of the name.

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?

With no output schema, the description compensates by describing the return (stored status, label, remedy policy for a failed paid capability), and the write semantics plus data-retention policy are stated. Minor gaps remain around idempotency/duplicate reports, but nothing blocks a correct 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% for 13 parameters, so the schema already documents every field. The description only groups them (required id/success; optional evaluation_id/purchase_ref links, token/tool-call/latency/cost counts, failure_reason with success false) without adding syntax, formats, or units beyond what the schema provides. Baseline 3 applies.

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 specific verb and resource (report an outcome for a capability) and immediately scopes it: 'Stored as AGENT REPORTED; it never changes evidence labels, trust or ranking.' The 'Not for' clause names the sibling tools that cover capability questions, so an agent can distinguish this from get_capability/get_benchmark.

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

Usage Guidelines5/5

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

Explicit 'Use when: you ran a capability, or decided not to, and can say whether the task succeeded' plus 'Not for: questions about a capability (get_capability, get_benchmark)'. Both the positive trigger and the exclusion with named alternatives are given, leaving nothing to inference.

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

All Agentic Keychain toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources