GET https://delvorn.site/api/x402/test-asset — public $0.05 x402 canary, no register, no API key. Returns a verifiable Delvorn receipt after payment. Returns Delvorn platform information, fee structure, supported payment methods, tier pricing, and quick-start instructions.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden and reveals important traits: it is a paid public endpoint, requires no registration or API key, and produces a verifiable receipt after payment. It does not disclose failure modes or whether repeated calls incur repeated charges, but the payment and no-auth behavior are clearly stated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is fairly compact, but it repeats 'Returns' and front-loads the canary/receipt detail before the actual platform-info purpose. It could be tightened by combining the receipt and platform-info statements into one clear sentence.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Because there is no output schema, the description needs to explain return values, and it does list fee structure, payment methods, tier pricing, and quick-start instructions. However, it introduces the test-asset canary and verifiable receipt without explaining how they relate to the platform information, leaving some ambiguity about what the response actually contains.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema is empty, so there are no parameter semantics to document. The description correctly implies no parameters are needed, and the baseline for a zero-parameter tool applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description ultimately states a concrete outcome: returns Delvorn platform information, fee structure, supported payment methods, tier pricing, and quick-start instructions. However, the opening focuses on the x402 test-asset canary and payment receipt, which could make an agent confuse this with a paid canary/purchase tool rather than a platform-info tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this is a low-friction public endpoint because it says 'public $0.05 x402 canary, no register, no API key.' It does not explicitly say when to choose this over siblings like get_asset, get_stats, or delvorn_canary, nor does it mention any exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct resources and the x402 lifecycle is split by clear verbs, but get_platform_info and delvorn_canary both describe the same public canary endpoint, creating overlap. buy_asset vs the x402 relay quote/fund flow also leaves some ambiguity about which purchase path to use, and list_asset vs browse_assets uses "list" in a confusingly different sense.
Names overwhelmingly follow a readable snake_case verb_noun pattern like buy_asset, get_asset, create_x402_relay_quote, and register_agent. The main exceptions are delvorn_canary, which has no verb, and list_asset, where the verb is overloaded and could be mistaken for a browse/list operation.
Thirteen tools is within a reasonable range for a marketplace plus payment-relay server, and most tools have a distinct role. The count is slightly high because platform info, stats, and the canary overlap in purpose, but none of the tools feel truly gratuitous.
The core lifecycle is covered: agent registration, asset listing/browsing/purchasing, and the x402 quote/fund/status/retry flow. Obvious gaps include unlisting or updating an asset and cancelling a relay payment, but these are workable limitations rather than severe dead ends.