Skip to main content
Glama

VouchSpec Agent Skill Evidence

by io.github.mordiaky
OverviewDiscussionsAdmin

Server Details

Read-only discovery for exact-commit Agent Skill validation, x402 payment, and signed receipts.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
mordiaky/vouchspec
GitHub Stars
1
Server Listing
VouchSpec Catalog MCP

TDQS

A3.8/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or misselection. The tool's purpose is clearly defined in its description, even though the set itself is minimal.

Naming Consistency3/5

A single tool name 'get_vouchspec_discovery' follows a verb_noun pattern ('get' + 'vouchspec_discovery'), but with only one tool, there is no pattern to evaluate consistency. The naming is acceptable but cannot be fully assessed.

Tool Count2/5

The server provides a single tool, which is extremely thin for a server named 'VouchSpec Agent Skill Evidence'. While it may serve a narrow purpose, it seems under-scoped for a server that likely supports a broader integration, and agents may need more tools to be useful.

Completeness1/5

The server appears to be about VouchSpec discovery, but there are no tools for actual interactions (e.g., create payment, check status, list receipts). The single tool only returns static instructions, so the surface is severely incomplete for any real workflow.

Available Tools

1 tool
get_vouchspec_discoveryGet VouchSpec discoveryA
Read-onlyIdempotent
Inspect

Return current agent-only pricing, x402 payment, request, receipt, and status instructions.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedget_vouchspec_discovery

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources