Skip to main content
Glama

Cite a registry entry

get_citation
Read-onlyIdempotent

Dated citation of a registry entry in APA and/or BibTeX, with its status and the date that status was observed. Data are CC BY 4.0, credit DiscoverIA.

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

Input Schema

NameRequiredDescriptionDefault
idYesEntry id (slug), e.g. 'gauss-sphere-packing-dim8', as returned by search_announcements.
langNoLanguage of titles, labels and texts: 'fr' (French) or 'en' (English). Default 'en'. Use the user's language.en
styleNo'apa', 'bibtex' or 'both'. Default 'both'.both

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly, idempotent, closed-world and non-destructive semantics, so the bar is lower, and the description still adds real context: the output includes the entry's status and the date that status was observed, plus a CC BY 4.0 licence with a required credit to DiscoverIA. It does not describe error behaviour for an unknown id.

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?

Two short sentences, front-loaded with what is returned and followed by the licence/attribution constraint. No filler, and every clause carries information an agent would otherwise have to guess.

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 usefully sketches the return content (formatted citation strings, status, observation date) and the attribution obligation. It falls short only on edge cases such as an invalid or unknown id, which is minor for a single-id read tool.

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%, with both enums (lang, style) and the id pattern fully documented in the schema, so baseline is 3. The description's 'APA and/or BibTeX' echoes the style parameter and adds nothing new beyond the schema.

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 states a specific verb and resource (cite a registry entry) and names the output formats (APA and/or BibTeX) plus the accompanying status/observation date. This is clearly distinct from sibling readers like get_announcement or get_frontier, though it doesn't explicitly name them.

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?

Usage is only implied: an agent can infer it should call this when a citation is needed, versus get_announcement for raw entry content. There is no explicit when-to-use/when-not statement or named alternative, which for such a simple read tool is adequate but not instructive.

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