Skip to main content
Glama

AMIRA — Africa Multiple Research Data

by io.github.AM-Digital-Research-Environment
OverviewDiscussionsAdmin

Get publication detail

get_publication
Read-onlyIdempotent

Publication metadata and citation export (BibTeX default). Full text is opt-in and paginated. Cite amira_url; DOI/repository links are additional sources.

Input Schema

NameRequiredDescriptionDefault
idYesPublication Omeka id or typed id publication:29919
citation_formatNoDefault bibtex; selects bibtex, ris or csl_json field
fulltext_offsetNoStart offset into the full text (chars), with include_fulltext
include_fulltextNoDefault false — set true to include the extracted full text
fulltext_max_charsNoMax full-text characters to return (default/max 25000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / id / anyOf
      Added value: +[
+  {
+    "maxLength": 1000,
+    "type": "string"
+  },
+  {
+    "type": "number"
+  }
+]
    • changedInput schema / properties / id / description
      Previous value: -"Publication Omeka o:id (legacy publication keys also work)"New value: +"Publication Omeka id or typed id publication:29919"
    • removedInput schema / properties / id / type
      Removed value: -[
-  "string",
-  "number"
-]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description isn't burdened with safety disclosure. It still adds real context beyond them: BibTeX is the default citation format, full text is opt-in and paginated, and amira_url is the canonical citation source with DOI/repository links as secondary.

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?

Three short, front-loaded sentences with no filler: it leads with what is returned, then the opt-in/pagination behavior, then citation guidance. Tight and well-ordered.

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?

Given the annotations carry the safety profile and no output schema exists, the description adequately covers the payload (metadata, citation formats, opt-in full text) for a single-record get. It leaves the mechanics of continuing pagination slightly implicit, so it is strong but not exhaustive.

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 schema already documents id, citation_format, and the fulltext parameters (defaults, min/max). The description's mention of BibTeX default and paginated full text largely mirrors what the schema states, adding little beyond the 3 baseline.

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 (get) and resource (publication) and clarifies the payload is metadata plus citation export, so the agent knows it returns a single publication's data rather than a list. It does not name the sibling search_publications to distinguish list-vs-detail retrieval, so it falls 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 Guidelines3/5

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

'Full text is opt-in and paginated' implies the retrieval context and how to expand results, but there is no explicit when-to-use guidance or exclusion versus search_publications / list_publication_facets. Usage is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AMIRA — Africa Multiple Research Data toolsInspect
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