Skip to main content
Glama

Find sourced reference dimensions

search_references
Read-onlyIdempotent

Search people, animals, prehistoric animals, objects, furniture, sports, vehicles and landmarks. Returns the recorded measurement axis, endpoints, source and artwork license.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds real value by disclosing the shape of the return payload — recorded measurement axis, endpoints, source and artwork license — which the annotations do not. It says nothing, however, about ordering, how many results come back by default, or whether an empty query returns everything, which matters for a search tool.

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?

Two compact sentences, front-loaded with the searchable domains and followed by the return payload. Every clause carries information; the only weakness is that the return-value sentence arrives without any framing about when results would be empty.

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 three-optional-parameter lookup with no output schema, the description covers the domain and the response shape but leaves key agent questions unanswered: what a query string matches, how results are ordered, and what happens with the default empty query. Adequate but with clear gaps given the 0% schema coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so none of the three parameters (query, limit, category) are documented in structured form, and the description does not compensate. It lists the category values, which merely restates the enum, and never explains what field 'query' matches against, whether matching is fuzzy or prefix, or what 'limit' does beyond the schema's default of 10 and maximum of 20.

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 specific verb (Search) and a concrete resource domain, enumerating the entity types searched and naming what comes back (measurement axis, endpoints, source, artwork license). That is enough to distinguish it from the sibling tools, which compute or compare heights rather than look up reference records, though the phrase 'reference dimensions' is only clarified at the end of the second sentence.

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?

When-to-use is only implied: an agent can infer this is the lookup tool for real-world sourced measurements, but there is no explicit statement of when to prefer it, no prerequisites, and no exclusions or pointers to the sibling tools. Nothing is misleading, but guidance must be inferred from the domain list.

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.

Resources