Lilambd Data for Agents

sound

World Music Instruments and Singing Styles. Cross-cultural music data for music apps, games, education, sound design and AI agents, built from open research archives. Routes: /names (q, limit, offset); /songs (q, genre, sound_source, region, society_id, limit, offset); /genres (q, limit, offset); /styles (society_id, var_id, code, region, limit, offset); /classes (q, limit, offset); /ensembles (q, region, country, limit, offset); /functions (function, region, limit, offset); /societies (q, region, country, lat, lon, limit, offset); /instruments (q, hs_class, hs_number, region, country, society_id, lat, lon, limit, offset); /styles/axes (q, var_id, limit, offset); /sound-sources (q, limit, offset); /instruments/{id}; /classes/{hs_code}; /societies/{society_id}. Paid $0.005 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": "sound"
  }
}

Input Schema

Name	Required	Description
`route`	Yes	One of: /names, /songs, /genres, /styles, /classes, /ensembles, /functions, /societies, /instruments, /styles/axes, /sound-sources, /instruments/{id}, /classes/{hs_code}, /societies/{society_id}. 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 3, 2026

TDQS

A3.7/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 disclose the two most consequential behaviors: every call costs $0.005 USDC through x402 (_meta["x402/payment"]), and sample=true returns a free 3-row preview. It also names the data provenance (open research archives). It stops short of rate limits, error/payment-failure behavior, and result-set size beyond the sample cap.

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?

Information-dense with no filler: a one-line domain statement, then the route/parameter matrix, then payment terms. The route list is a dense semicolon-separated run-on that is harder to scan than a structured list, but every clause earns its place and payment details are correctly deferred to the end.

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 polymorphic router with a nested free-form params object and no output schema, the definition covers routing, per-route parameters, cost, and the free sample path, which is enough to call it correctly for a read. What is missing is return-shape guidance per route (record fields, pagination behavior, what /styles/axes returns), which matters precisely because no output schema exists.

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 the baseline is 3. The description does add genuine value by mapping which query parameters apply to which route (e.g. /instruments accepts hs_class, hs_number, lat, lon while /names accepts only q, limit, offset), which the flat additionalProperties schema cannot express. However it never explains value formats (hs_class codes, var_id, society_id) or pagination semantics for limit/offset.

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 names the domain concretely ('World Music Instruments and Singing Styles', 'Cross-cultural music data') and lists 14 concrete routes, so an agent knows it is a music-ethnography data gateway rather than a generic fetch tool. It does not explicitly contrast itself with the many sibling API wrappers (airports, colors, languages, etc.), leaving differentiation to be inferred from the domain noun.

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?

Usage is implied only through the route inventory: to get songs you call /songs, to get instruments you call /instruments, and sample=true gives a free preview instead of paying. There is no explicit statement of when to prefer this tool over a sibling or when a given route should be avoided, and no prerequisites are spelled out.

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?