Skip to main content
Glama
Sign In
x402-wallet-mcp

x402-wallet-mcp

by kato9292929
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get resource details

get_resource_details
Read-only

Fetch a service's full Bazaar record by resource URL, including accepted payment options, price, description, and input/output schema.

Instructions

Full Bazaar record for one service: accepted payment options, price, description and input/output schema.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "resource": "<resource>"
    },
    "name": "get_resource_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceYesThe resource URL from list_bazaar_resources

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful content disclosure (what fields the record includes) but says nothing about failure behavior for an unknown or malformed resource URL, which matters for an open-world lookup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the main statement of what is returned and zero padding. The noun-phrase style lacks an explicit verb, but nothing is wasted.

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?

With no output schema, the description carries the burden of describing return values, and it does so by listing the record's fields. For a one-parameter read-only lookup this is nearly complete; only error/not-found behavior is unaddressed.

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

Parameters3/5

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

Schema coverage is 100% and the single parameter is documented in-schema as a URI drawn from list_bazaar_resources. The description adds no additional meaning about the parameter, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (the full Bazaar record for one service) and enumerates what the record contains: payment options, price, description, and input/output schema. The singular 'one service' implicitly distinguishes it from list_bazaar_resources, though no sibling is named explicitly.

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?

Usage is only implied by the word 'one service' — an agent can infer this is the detail fetch that follows a list call. There is no explicit guidance on when to prefer this over check_payment_requirements or make_x402_request, and no stated prerequisites.

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