Skip to main content
Glama
QuincyGB

ListSmith MCP

by QuincyGB
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGENT_KEY_FILENoPath to a file containing the EVM private key. Alternative to AGENT_PRIVATE_KEY.
LIST_SMITH_URLNoService base URL override (default: production).
AGENT_PRIVATE_KEYNoEVM private key (0x...) of a wallet holding USDC on Base. Used locally to sign the x402 EIP-3009 authorization. Required for paid calls.
LIST_SMITH_FIX_MAX_AMOUNT_UNITSNoSpend guard for /v1/fix in USDC micro-units (default 500000 = $0.50, the known price).
LIST_SMITH_GRADE_MAX_AMOUNT_UNITSNoSpend guard for /v1/grade in USDC micro-units (default 100000 = $0.10, the known price).

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_gradeA

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.
list_fixA

Repair one x402 route's Bazaar discovery metadata.

Calls ListSmith POST /v1/fix ($0.50 USDC on Base via x402).
Returns a complete repaired discovery package — a full output
schema inferred from your sample, a sub-500-char description with
a use-when sentence, OpenAPI and well-known snippets, and paste-in
instructions. The package ships only if it passes both x402 SDK
validators.

Args:
    resource_url: Full URL of the x402 resource to repair.
    sample_output: One real response body from the endpoint
        (required). The repaired output schema is inferred from
        this sample only — nothing is invented.
    name: Optional display name for the generated description;
        derived from the URL when omitted.
    category: Optional category (e.g. token-risk, search, data,
        media, monitoring) used to phrase the description's
        use-when sentence.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A4.5/5.0

Scored across 2 tools

Disambiguation4/5

list_grade (diagnosis) and list_fix (repair) target clearly different outcomes and the descriptions explicitly cross-reference each other ('Use list_fix when you want the repair'), so misselection is unlikely. The only friction is semantic: an agent could briefly read 'list_grade' as 'enumerate grades' before the description corrects it.

Naming Consistency4/5

Both tools use the same snake_case list_<verb> pattern, so the set is internally consistent. The chosen verb ('list') is semantically wrong for both operations (grade / fix), which is a minor deviation from the ideal verb_noun accuracy, but it is applied uniformly.

Tool Count3/5

Two tools is thin for a server with a paid two-step workflow; there is no ungraded/ungraded-batch entry point or overview tool. It is a defensible minimal surface (diagnose, then repair), but it sits at the borderline of the '1-2 tools feels thin' band.

Completeness4/5

The grade -> fix loop covers the full lifecycle for a single x402 route: detection, itemized defects, and a validated repair package, with no dead end. Gaps are minor and workaroundable: no batch grading across multiple routes, no way to re-fetch a previously generated repair, and sample_output is required for fix but optional for grade.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources