Lilambd Data for Agents

pet-entry

Pet entry: can my dog or cat cross this border in time?. Official rules for taking a pet dog, cat or ferret into another country: microchip, rabies shots, blood test and waiting days, advance notice, papers, quarantine, and the shortest days from scratch to legal entry. Every row cites the government page it was read from. Facts only, not veterinary or legal advice. Routes: /answer (to*, from, species, days, vaccinated_in); /country (to*); /countries. 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": "pet-entry"
  }
}

Input Schema

Name	Required	Description
`route`	Yes	One of: /answer, /country, /countries. 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 2, 2026

TDQS

A4/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 burden and does well: it discloses the x402 payment mechanism, the $0.5 USDC per-call cost, the free 3-row sample escape hatch, data provenance (every row cites a government page), and a facts-only disclaimer. It stops short of describing latency, error/payment-failure behavior, or response shape.

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?

Dense but front-loaded: purpose first, then data content, provenance, route/param map, then pricing. The opening 'Pet entry: can my dog or cat cross this border in time?' mildly duplicates the following 'Official rules for taking a pet dog, cat or ferret' sentence, a small amount of waste in an otherwise efficient block.

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?

Covers what the tool returns conceptually, provenance, cost model, free preview, and route/param mapping — strong for a tool with no annotations and no output schema. The main residual gap is distinguishing what /country returns versus /answer.

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?

The schema's `params` is a generic string map with a misleading example ({"q":"tokyo","limit":"50"}), so the description's per-route param listing (to*, from, species, days, vaccinated_in for /answer; to* for /country) adds real meaning the schema lacks. It still doesn't state value formats (country code standard, date format) for those params.

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 concrete resource and scope: official pet-import rules (microchip, rabies shots, blood test, quarantine, entry timing) backed by government citations. The verb is implicit ('can my dog or cat cross this border') rather than a clean action verb, and it does not name the closest sibling (travel-meds) to differentiate, keeping it at 4.

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

Usage Guidelines4/5

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

Enumerates the three routes with their required params (/answer vs /country vs /countries), which effectively tells the agent which route to pick for which question. It also states the free-preview path (sample=true) and the paid path, but gives no when-not guidance or sibling comparison.

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?