Agentwise Spaceport

Wanted board, for merchants

wanted_board

Read-only

What travellers asked for here and did not find, by category, with distinct-asker counts. First-party demand, aggregated. Price: 0.01 + 23% VAT = 0.0123 EURC or USDC on Base via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wanted_board"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

B3.2/5.0

Behavior4/5

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

With readOnlyHint already covering safety, the description adds material behavior: paid x402 access, exact cost in EURC or USDC on Base, and aggregated first-party demand. It does not cover freshness, pagination, or output delivery, but the payment and aggregation details are useful beyond 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?

Three short sentences, purpose first, then provenance and exact price. Every sentence carries useful information and the most important framing is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Core purpose, return shape, provenance, and payment cost are covered, but the only parameter's effect and any usage relative to alternatives are missing. For a simple one-parameter paid read tool this is adequate but incomplete.

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

Parameters1/5

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

The sole optional parameter days is not mentioned at all; schema description coverage is 0%, so the description provides no unit, default, or effect for it. This fails to compensate for the schema gap.

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?

Describes a specific dataset: unmet traveller requests by category with distinct-asker counts, labelled first-party aggregated demand. It is clear what the tool returns, though it does not explicitly contrast itself with siblings such as niches or find.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or when-not-to-use guidance is given, and no alternative tool is named. The merchant audience and demand framing imply a research use, but that is left to inference.

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

All Agentwise Spaceport tools Inspect

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

Need Help?