Skip to main content
Glama
QuincyGB

ListSmith MCP

by QuincyGB
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_grade

Grades one x402 route's Bazaar discovery metadata: returns SDK validation verdicts, a schema-quality score, itemized defects with severities, and a 0-100 grade. Diagnosis only, no repairs.

Instructions

Grade one x402 route's Bazaar discovery metadata.

Calls ListSmith POST /v1/grade ($0.10 USDC on Base via x402).
Returns SDK validation verdicts, a schema-quality score, itemized
defects with severities, and a 0-100 grade. Diagnosis only — no
repaired content. Use list_fix when you want the repair.

Args:
    resource_url: Full URL of the x402 resource to grade.
    sample_output: Optional real response body from the endpoint;
        when supplied, it is also checked against the endpoint's
        published output schema.

Input Schema

NameRequiredDescriptionDefault
resource_urlYes
sample_outputNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the underlying endpoint (POST /v1/grade), a concrete paid-call cost ($0.10 USDC on Base via x402), and the shape of the verdict returned. The paid-invocation requirement is critical context an agent would otherwise not know before calling.

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-loaded with the action, then cost, then return shape, then the sibling routing, then params. The Args block is not wasted redundancy here because the schema is empty, so it is the only source of parameter documentation.

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?

Covers the action, the payment cost, the returned verdicts/score/defects/grade, the diagnosis-only constraint, and the repair alternative. An output schema exists, yet the description still summarizes the return shape usefully; nothing needed to invoke correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — sample_output has no type or description at all — so the description must compensate, and it does: resource_url is defined as a full URL, and sample_output is explained both as an optional real response body and as the trigger for the extra output-schema check.

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 — grade one x402 route's Bazaar discovery metadata — and immediately names the sibling list_fix as the repair counterpart, so an agent can distinguish the two without opening either schema.

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?

Explicitly frames the tool as diagnosis only with no repaired content, then routes the agent: 'Use list_fix when you want the repair.' The selection condition between the two siblings is fully stated.

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

Deploy Server

Other Tools