Lilambd Data for Agents

price-check

x402 API Price Check. Price your agent-facing API against the live market in one call. Routes: / (q*, price). Paid $0.5 USDC per call via x402 (_meta["x402/payment"]); set sample=true for a free 3-row preview.

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": {
      "route": "<route>"
    },
    "name": "price-check"
  }
}

Input Schema

Name	Required	Description
`route`	Yes	One of: /. Replace {placeholders} with a value, e.g. /search or /HND.
`params`	No	Query parameters, e.g. {"q":"tokyo","limit":"50"}
`sample`	No	Free preview, max 3 rows

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With no annotations, the description carries the full load, and it does disclose the most consequential behavior: this is a paid operation ($0.5 USDC per call through x402 _meta['x402/payment']) with a free tier capped at 3 rows. It does not describe failure behavior, rate limits, or what a paid result contains beyond the 3-row preview.

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?

Three compact sentences with the cost and the free-sample escape hatch front-loaded; there is little filler. The 'Routes: / (q*, price)' clause is dense jargon that costs more reading effort than the value it delivers.

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?

For a 3-parameter tool with a nested free-form params object, a payment flow, and no output schema or annotations, the description covers pricing and the sample flag but leaves the route semantics and expected response shape unexplained. An agent knows it may pay, but not confidently what it gets in return.

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 description coverage is 100%, so route, params, and sample are already documented in structured form, making 3 the baseline. The description only restates the sample behavior ('free 3-row preview') and adds no meaning about what 'q*' or the returned 'price' are, or how the nested params object is interpreted.

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 states a specific verb and resource ('Price your agent-facing API against the live market in one call'), so an agent can grasp the intent without opening the schema. However, it does not differentiate the tool from close siblings such as 'prices', 'list_apis', or 'market-gaps', and the cryptic 'Routes: / (q*, price)' fragment muddies rather than clarifies what is actually returned.

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?

It gives useful cost-related guidance: the call costs $0.5 USDC via x402, and setting sample=true yields a free 3-row preview, which implies a cheap-first-probe workflow. It stops short of saying when to choose this over sibling tools like 'prices' or 'list_apis', or what prerequisites the payment flow needs.

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

All Lilambd Data for Agents 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?