Skip to main content
Glama

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.

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_publication"
  }
}

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_similarNoAdd up to 5 similar records, each explained
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. 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. Changed2 schema fields changed
    • removedInput schema / properties / fulltext_max_chars / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / fulltext_offset / maximum
      Removed value: -9007199254740991
  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: -"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"
      -]
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description usefully adds that BibTeX is the default export, that full text is off by default and paginated rather than dropped, and which URL is authoritative for citation. Missing only return-size or rate-limit framing, which is minor for a read-only tool.

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 primary capability and the defaults, with zero filler. The telegraphic citation rule is dense but earns its place.

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 six fully documented parameters, no output schema, and annotations covering safety, the description supplies enough to call it correctly. It could be richer about what include_similar returns, but the schema carries that load.

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 every parameter is already self-documenting, and the description largely restates what the schema says (BibTeX default, opt-in paginated full text). It adds no new semantics such as what 'explained' similar records contain or how offsets interact with the 25000-char cap.

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?

Names the concrete resource (publication metadata) and the secondary output (citation export), plus states the full text is opt-in. It does not distinguish itself from siblings like get_text_passages or get_similar_items, so an agent must infer that boundary, but the core purpose is clear.

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?

Provides citation-specific guidance (cite amira_url; DOI/repository links are additional sources) and notes full text is opt-in, which implies a default lightweight call. It never states when to prefer a sibling such as get_fulltext_map or get_similar_items over enabling include_fulltext/include_similar here.

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.