Skip to main content
Glama

Citation

cite
Read-onlyIdempotent

Return the recommended citation line for a version, its version DOI (if it has one), the DOI that covers all versions, and the licence.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cite"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNoRegistry version, for example "1.4.1" (a leading "v" is accepted). Default: the latest published version (1.4.1). Available: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.3.1, 1.4.0, 1.4.1.

Output Schema

NameRequiredDescriptionDefault
urlNo
noteNo
scopeNoScope of the registry: what the entries are and are not.
licenseYes
versionYes
citationYes
releasedNo
attributionNoCC BY 4.0 attribution: how an answer that uses the entries names the source.
doi_versionNo
license_urlNo
doi_all_versionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / version / description
      Previous value: -"Registry version, for example \"1.4.0\" (a leading \"v\" is accepted). Default: the latest published version (1.4.0). Available: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.3.1, 1.4.0."New value: +"Registry version, for example \"1.4.1\" (a leading \"v\" is accepted). Default: the latest published version (1.4.1). Available: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.3.1, 1.4.0, 1.4.1."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine behavioral context beyond that by disclosing that the version DOI is conditional ('if it has one') and that a licence is returned alongside the all-versions DOI.

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?

One front-loaded sentence listing the four returned artifacts in a natural reading order with zero filler. Nothing is repeated from the schema or annotations, and nothing could be cut without losing meaning.

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?

Return values are declared by the output schema and the version behavior is fully carried by the input schema, so the description is nearly complete for this low-complexity, single-optional-parameter tool. The only residual gap is the absence of any routing guidance among the several sibling lookup tools.

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% and the single optional 'version' parameter already documents the accepted format, the leading 'v' tolerance, the default of the latest published version, and the full list of available versions. The description adds no parameter guidance 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 resource (the version's citation) and enumerates exactly what comes back: citation line, version DOI, all-versions DOI, and licence. That is far more informative than a tautology, though it never contrasts itself with siblings such as get_mechanism or list_versions, so it stops short of full differentiation.

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 that this is the tool to call when a formatted citation or DOI is needed. There is no explicit when-to-use statement, no when-not-to-use, and no named alternative for related needs like resolving a name to a version.

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.