buyer_capabilities
Inspect AgentWork's disabled-by-default purchasing policy and future Cloudflare Wallet adapter status.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
AgentWork Outcome Router
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full responsibility. 'Inspect' implies a read-only operation, but it does not explicitly state side effects, auth requirements, or whether it only returns status. The 'disabled-by-default' trait refers to the policy, not the tool's behavior.
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?
A single, well-structured sentence that communicates the tool's function with no wasted words. It is appropriately front-loaded.
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?
While the tool is simple with no parameters, the description omits any indication of what the output will look like or how the result is structured. Given the lack of an output schema, this information would be valuable for a complete understanding.
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?
The tool has zero parameters, so the schema provides full coverage by default. The baseline of 4 applies, and the description does not need to add parameter details.
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 description uses a specific verb 'Inspect' and clearly identifies the resources: AgentWork's purchasing policy and Cloudflare Wallet adapter status. This distinguishes it well from siblings focused on blocked outcomes and search operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, and there are no exclusions or context clues. The agent must infer usage solely from the tool's purpose.
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.
TDQS
A3.5/5.0
Disambiguation3/5
Most tools are separated by lifecycle stage, and the descriptions are detailed, but resolve_blocker and request_outcome_execution both accept work the agent cannot complete, making their boundary subtle. get_blocker_resolution and get_outcome_execution are also both private status readers, so some overlap exists even though descriptions help.
Naming Consistency4/5
The set is mostly consistent with snake_case verb_noun names like search_work, select_blocker_offer, and report_blocker_outcome. buyer_capabilities is a bare noun phrase rather than a verb_noun, and submission verbs vary between resolve and request, but overall the naming remains predictable.
Tool Count5/5
Ten tools is well within the well-scoped range for a workflow server. Each tool supports the blocker lifecycle, execution status, or work/service discovery, and none feels gratuitous.
Completeness4/5
The core workflow is fully represented: resolve a blocker, discover routes, select an offer, execute, read evidence, and report outcomes. There is no explicit cancel or request-history tool, and some search/discovery tools are not tied to a follow-up action, but these are minor gaps rather than dead ends.