Skip to main content
Glama

Search the AMIRA collection

search
Read-onlyIdempotent

Ranked search across items, publications, videos, podcasts, projects and sections. Returns typed IDs, titles and citation URLs. Fetch selected records for evidence.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 10, max 50
queryYesA few keywords, names, places or themes — e.g. 'Yoruba architecture'. Terms are matched individually, so concise queries beat full sentences
typesNoRestrict to these record kinds

Output Schema

NameRequiredDescriptionDefault
resultsYes
effective_limitNo
requested_limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / results / items / properties / url / description
      Previous value: -"The AMIRA/Omeka public record page"New value: +"The AMIRA/Omeka record page"
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / results / items / additionalProperties
      Removed value: -false
  3. Changed1 schema field changed
    • removedInput schema / properties / limit / maximum
      Removed value: -9007199254740991
  4. Changed1 schema field changed
    • changedOutput schema / properties / results / items / properties / id / description
      Previous value: -"Typed record id, e.g. 'item:7392'"New value: +"Typed record id, e.g. 'item:9902'"
  5. Changed3 schema fields changed
    • addedInput schema / properties / query / maxLength
      Added value: +1000
    • addedOutput schema / properties / effective_limit
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / requested_limit
      Added value: +{
      +  "type": "number"
      +}
  6. First observed

TDQS

A3.6/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 openWorldHint=false, so the safety profile is fully covered structurally. The description adds the ranking behavior and the shape of returned identifiers, which is genuinely useful, but it does not disclose ordering stability, result cap behavior, or coverage limits (e.g. that person records are not among the searchable kinds).

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?

Three short sentences, front-loaded with the scope, then the return shape, then the follow-up action. No redundant or filler wording; each sentence carries distinct information.

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?

With an output schema present and full annotation coverage, the description need not explain return values or safety, and it correctly focuses on scope and the search-then-fetch workflow. It is slightly thin on how this relates to the many typed search siblings, which is the main thing an agent would still have to guess.

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%: query formatting advice ('a few keywords... concise queries beat full sentences'), the types enum, and the limit default/max are all documented in the schema itself. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 a specific verb and resource set — ranked search across items, publications, videos, podcasts, projects and sections — and states what comes back (typed IDs, titles, citation URLs). It is clearly distinguishable from a fetch tool, though it never explicitly contrasts itself with the many typed search siblings (search_persons, search_videos, etc.), which is the one differentiation gap.

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?

The final sentence, 'Fetch selected records for evidence,' implies the intended two-step workflow (search broad, then fetch by ID), which is useful implied usage guidance. However, there is no explicit statement of when to prefer this cross-type search over the per-type siblings, and no exclusions or prerequisites.

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.