Skip to main content
Glama

Zenodo Record

zenodo_record
Read-onlyIdempotent

Single record by Zenodo id.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered and the description adds nothing on top of that. It does not mention what happens for an unknown id, whether records are cached, or what the response contains, leaving no behavioral value beyond the structured hints.

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?

Five words with zero filler and the key resource stated first. The tradeoff is that the terseness borders on under-specification, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and annotations cover the safety profile. For a one-parameter lookup this is close to adequate, but the ambiguity about the id type and the absence of any contrast with sibling tools leaves meaningful gaps.

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?

The single parameter has 0% schema description coverage, so the description does minor work by qualifying the id as a "Zenodo id," clarifying the namespace versus internal identifiers, and the schema example ("1234567") reinforces the numeric string form. It does not state whether the id is a record id versus a concept/DOI id, which is a real ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Single record by Zenodo id" conveys the resource (a Zenodo record) and the lookup key, and the word "single" implicitly contrasts with the sibling zenodo_search. However, it is a noun fragment with no verb and never names zenodo_search or record_files, so the agent must infer that this is a retrieval operation.

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 explicit when-to-use guidance, no condition distinguishing it from zenodo_search (find records) or record_files (get files for a record), and no mention of prerequisites or error behavior for a nonexistent id. The agent must derive usage entirely from the name and siblings.

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.