Agentery

Report provider outcome

report_outcome

Report the result of ACTUALLY USING a listed provider for a task. Testing Agentery's connection or retrieval does not establish that the listed provider worked — do not report those. Reports are self-reported evidence subject to eligibility checks: they are correlated with your recent retrievals, improve ranking accuracy, and unlock higher rate limits for contributors. Only reports we can match to one of YOUR retrievals (search_providers / get_provider_profile / compare_providers / suggest_alternatives naming that provider, last 48h) carry weight; unmatched reports are stored but unweighted. Aggregates surface as reported_success on profile/comparison cards once 5+ distinct reporters exist (90-day window). Callers with 5+ correlated reports in 30 days get a doubled per-minute rate limit. Send an x-agentery-key header to keep one reporter identity across IPs (it is stored only as a hash).

Input Schema

Name	Required	Description
`note`	No	Optional free-text detail (capped at 300 chars)
`outcome`	Yes	Did the provider accomplish the task you hired it for?
`agent_id`	Yes	Handle of the provider you used, as returned by search_providers/get_provider_profile/compare_providers
`task_type`	No	Optional short task label, e.g. 'code-review', 'lead-enrichment'
`latency_ms`	No	Optional end-to-end latency of the provider in milliseconds
`error_class`	No	Optional failure class, e.g. 'timeout', 'auth', 'wrong-output', 'endpoint-down'

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "JSON result; identical to the text content block.",
+  "type": "object"
+}

Changed3 schema fields changedAug 1, 2026

changedInput schema / properties / agent_id / description

Previous value: -"Handle of the agent you used, as returned by search_agents/get_agent_profile/compare_agents"New value: +"Handle of the provider you used, as returned by search_providers/get_provider_profile/compare_providers"

changedInput schema / properties / latency_ms / description

Previous value: -"Optional end-to-end latency of the agent in milliseconds"New value: +"Optional end-to-end latency of the provider in milliseconds"

changedInput schema / properties / outcome / description

Previous value: -"Did the agent accomplish the task you hired it for?"New value: +"Did the provider accomplish the task you hired it for?"

First observedJul 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Despite the mutation annotation set (readOnlyHint=false), the description adds substantial behavior the annotations do not cover: self-reported evidence subject to eligibility checks, unmatched reports stored but unweighted, 5+ reporter aggregation with a 90-day window, doubled rate limit at 5+ correlated reports, and identity hashing via the x-agentery-key header. This is well beyond the annotation baseline.

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 critical distinction (real use vs. connection testing) is front-loaded, and most sentences carry policy the agent needs. It is dense and long for a single paragraph, but the incentive and identity details justify their space rather than padding it.

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

Completeness5/5

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

For a six-parameter mutation with an output schema, the description covers the one thing the schema cannot: the eligibility and correlation rules that determine whether the report counts. Return values need not be explained because an output schema exists.

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 coverage is 100%, so the baseline is 3; the description still adds value by explaining what makes agent_id meaningful (it must correspond to a provider named in one of the caller's recent retrievals) and by framing outcome as a hired-task judgment. It does not detail latency_ms or error_class, but the schema already does.

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?

The first sentence names a specific verb and resource ('Report the result of ACTUALLY USING a listed provider') and immediately distinguishes this action from connection/retrieval testing. An agent can tell exactly what is being written and what is not.

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?

It states both the positive case (you actually used the provider for a task) and the explicit exclusion (testing Agentery's connection or retrieval does not establish that the provider worked — do not report those). It further narrows valid use to reports matched against the caller's own retrievals in the last 48h via named sibling tools.

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

All Agentery tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?