Skip to main content
Glama

Get research item detail

get_research_item
Read-onlyIdempotent

Research-item metadata, linked entities, rights, media files, IIIF manifest and a generated citation (BibTeX/RIS/CSL-JSON). Long fields cap at 25,000 characters.

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": {
      "id": "<id>"
    },
    "name": "get_research_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOmeka id (the number ending its amira_url, e.g. 9902) or a typed id such as research_item:9902
citation_formatNoExport format for the generated citation: bibtex (default) → `bibtex`, ris → `ris`, csl-json → `csl_json`
include_similarNoAdd up to 5 similar records, each explained

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / include_similar
      Added value: +{
      +  "description": "Add up to 5 similar records, each explained",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Omeka id (the number ending its amira_url, e.g. 7392) or a typed id such as research_item:7392"New value: +"Omeka id (the number ending its amira_url, e.g. 9902) or a typed id such as research_item:9902"
  3. Changed3 schema fields changed
    • addedInput schema / properties / id / anyOf
      Added value: +[
      +  {
      +    "maxLength": 1000,
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  }
      +]
    • changedInput schema / properties / id / description
      Previous value: -"The item's Omeka o:id — the number ending its amira_url, e.g. 7392. Legacy DRE keys also work"New value: +"Omeka id (the number ending its amira_url, e.g. 7392) or a typed id such as research_item:7392"
    • removedInput schema / properties / id / type
      Removed value: -[
      -  "string",
      -  "number"
      -]
  4. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real value beyond that: it discloses the composition of the response (linked entities, rights, IIIF manifest, citation formats) and, importantly, that long fields are truncated at 25,000 characters — a caveat an agent cannot learn from structured fields. It does not say what happens for an unknown or malformed id, which keeps it from a 5.

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 short sentences with no filler, and the payload list is front-loaded ahead of the truncation caveat. The first sentence is a bare noun phrase rather than a clause, which reads slightly telegraphic, but nothing is wasted.

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 no output schema, the description carries the burden of describing return content and does so by listing the major components and the truncation limit. For a three-parameter, single-id read tool this is close to sufficient; only error/not-found behavior and the nature of the include_similar payload are left unstated.

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 all three parameters are already documented in the schema, including the id format and the citation_format enum mapping. The description only echoes the citation formats already listed in the schema and says nothing about include_similar or the accepted id forms, so it adds no meaning beyond the schema. Baseline 3 is appropriate.

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 enumerates a specific resource and its payload — metadata, linked entities, rights, media files, IIIF manifest, generated citation — which tells an agent precisely what a call returns and implicitly sets it apart from list/search siblings. It never uses an explicit verb ("get" appears only in the title) and does not name which sibling to use for section-level or search access, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. Nothing tells the agent to prefer this over search_research_items when it lacks an id, or over get_research_section when it needs section-level content. Usage is only inferable from the presence of a required id parameter.

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.