How to buy DwellData data
how_to_buyFree: x402 payment instructions — endpoints, prices in USDC on Base mainnet, and the discovery documents.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
real-estate-data
by io.dwelldata
TDQS
B3.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose behavioral traits. It only mentions 'Free: x402 payment instructions' and fails to describe side effects, authentication, or response behavior.
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?
Single sentence is concise but could be better structured (e.g., listing items). Front-loaded with 'Free' is useful.
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?
Given no parameters and no output schema, the description covers the purpose but lacks context on format, prerequisites, or post-use steps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, baseline is 4. The description adds meaning about what the tool provides without needing to document parameters.
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?
The description clearly states it provides payment instructions, endpoints, prices, and discovery documents for buying DwellData data. It distinguishes from sibling 'get_catalog' in scope, but the verb is implied rather than explicit.
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 guidance on when to use this tool versus alternatives like 'get_catalog'. The description implies use for purchasing data, but lacks explicit when/when-not or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.4/5.0
Disambiguation5/5
get_catalog provides data coverage and samples, while how_to_buy gives payment instructions. Their purposes are entirely distinct with no overlap.
Naming Consistency4/5
Both names use underscores and are descriptive, but 'get_catalog' follows a verb_noun pattern while 'how_to_buy' is a phrase. Mostly consistent with a minor deviation.
Tool Count3/5
With only 2 tools, the server covers catalog browsing and purchase instructions, which may be reasonable for a discovery-focused API, but it feels thin for a data provider.
Completeness2/5
The server lacks tools to actually retrieve purchased data feeds (e.g., get_deals, get_signals). Users can browse and buy but not access the core product, leaving a significant gap.