Lilambd Data for Agents

travel-meds

Travel meds: can I bring this medicine into this country?. Official rules for travellers carrying personal medicines across borders: how many days of supply, which classes need a permit, how and how early to apply, documents, and what is banned outright. Every row cites the government page it was read from and when. Facts only, not medical or legal advice. Routes: /answer (country*, class, days); /country (country*); /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": "travel-meds"
  }
}

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.4/5.0

Behavior4/5

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

With no annotations, the description carries the burden and discloses important behavior: paid $0.5 USDC per call via x402, free 3-row preview with sample=true, facts-only stance, and source citations with dates. It does not cover rate limits, error behavior, or full return structure, so it is strong but not exhaustive.

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?

The description is front-loaded with the core question, then quickly covers scope, output content, citations, disclaimers, routes, payment, and preview. Every sentence adds useful selection or invocation context without wasted prose.

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?

For a no-output-schema tool, it describes the substantive answer content: days of supply, permit classes, application timing, documents, and banned items. It also explains citations and payment, but does not specify the exact row structure or error responses, leaving a small completeness gap.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds route-specific parameter semantics: /answer takes country*, class, and days; /country takes country*; /countries takes none. It also explains the sample preview flag, though it leaves country-code formatting and the params-object mapping somewhat implicit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and question: official rules for travellers carrying personal medicines across borders. It immediately distinguishes the tool from unrelated siblings like airports, colors, and exchanges by naming the exact domain and the details covered.

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?

It lists the available routes and their required parameters, which guides endpoint selection, and explains that sample=true gives a free preview before paying. It does not explicitly state when not to use the tool or name alternatives, but the usage context is clear.

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?