Get VouchSpec discovery
get_vouchspec_discoveryRead-onlyIdempotent
Return current agent-only pricing, x402 payment, request, receipt, and status instructions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
VouchSpec Agent Skill Evidence
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate a safe read operation (readOnlyHint, destructiveHint). The description adds behavioral context by specifying exactly what kind of instructions are returned, which is valuable beyond the annotations.
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?
Single sentence, concise, front-loads the action and resource. No unnecessary words.
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?
Given the tool has no input schema, no output schema, and no parameters, the description adequately covers the output content. It could be more detailed (e.g., format of instructions), but provides sufficient context for an agent to understand the tool's purpose.
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?
No parameters exist (0 params), so baseline score of 4 applies. The description adds no parameter details as there are none to describe.
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 clearly states the action (Return) and resource (current agent-only pricing, x402 payment, request, receipt, and status instructions). It is specific and leaves no ambiguity about what the tool outputs.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives, but the purpose is clear enough for self-explanatory use. The absence of sibling tools reduces the need for differentiation, yet still no usage context is provided.
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
A4.1/5.0
Disambiguation5/5
Only one tool exists, so there is no possibility of ambiguity or confusion between tools.
Naming Consistency5/5
The single tool uses a clear verb_noun snake_case pattern ('get_vouchspec_discovery'), which is consistent and descriptive.
Tool Count3/5
With only one tool, the server feels thin for a broader domain like 'skill evidence', but it may be appropriate if the server's scope is narrowly limited to providing discovery instructions.
Completeness3/5
The tool returns a set of instructions (pricing, payment, request, receipt, status), which covers the discovery aspect, but lacks any action-oriented tools (e.g., submitting requests or checking specific statuses), leaving potential gaps.