zenodo-mcp-server

Look up Zenodo filter ids

zenodo_lookup_vocabulary

Read-onlyIdempotent

Resolve names to the ids zenodo_search_records filters on, and browse Zenodo's reference vocabularies: communities (slug), funders (ROR id), awards and grants (award id), licenses (license id), and resource types (type id). Search by name, acronym, or keyword; awards can be scoped to one funder. Each entry names the zenodo_search_records parameter its id feeds.

Input Schema

Name	Required	Description
`page`	No	Result page, starting at 1. Only the first 10,000 entries of a list are reachable, so the last reachable page is 10,000 ÷ size rounded up (400 at size 25).
`size`	No	Entries per page, at most 25 per call; larger values return 25.
`query`	No	Name, acronym, or keyword, e.g. "SYMBA", "wellcome", "mit", "journal article". For resource_types every word must appear in the type id or label. Omit to browse the vocabulary.
`funder`	No	awards only: scope grants to one funder, given as a ROR id (00k4n6c32), a ROR URL, or a Crossref Funder DOI (10.13039/100000002). Resolve a funder name to its ROR id with vocabulary funders first.
`vocabulary`	Yes	Which vocabulary to search: communities, funders, awards (grants), licenses, or resource_types. Case, spaces, hyphens, and underscores are ignored when matching, and the singular (funder, license, resource type) and grants are accepted.

Output Schema

Name	Required	Description
`cap`	No	Page size applied (at most 25).
`page`	No	Page returned.
`size`	No	Page size applied: size, or 25 when size asked for more.
`error`	No	Present when the call failed. Absent on success.
`query`	No	The query as applied; absent when browsing.
`shown`	No	Entries returned on this page.
`total`	No	Total entries matching the query.
`notice`	No	Guidance on empty results, ambiguous funders, the 10,000-entry window, the 25-per-call size cap, or further pages.
`entries`	No	Matching entries for this page.
`has_more`	No	True when another page of reachable entries follows.
`next_page`	No	The next page number, when has_more.
`reachable`	No	Entries reachable by paging: min(total, 10,000).
`truncated`	No	True when more reachable entries follow this page.
`totalCount`	No	Total entries matching the query.
`vocabulary`	No	The vocabulary searched.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 18, 2026

changedInput schema / properties / page / description

Previous value: -"Result page, starting at 1."New value: +"Result page, starting at 1. Only the first 10,000 entries of a list are reachable, so the last reachable page is 10,000 ÷ size rounded up (400 at size 25)."

changedInput schema / properties / size / description

Previous value: -"Entries per page (1–25)."New value: +"Entries per page, at most 25 per call; larger values return 25."

changedInput schema / properties / size / maximum
```
Previous value: -25New value: +10000
```

changedOutput schema / anyOf

Previous value: -[
-  {
-    "not": {
-      "required": [
-        "error"
-      ]
-    },
-    "required": [
-      "vocabulary",
-      "total",
-      "page",
-      "size",
-      "has_more",
-      "entries",
-      "truncated",
-      "shown",
-      "cap",
-      "totalCount"
-    ]
-  },
-  {
-    "required": [
-      "error"
-    ]
-  }
-]New value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "vocabulary",
+      "total",
+      "reachable",
+      "page",
+      "size",
+      "has_more",
+      "entries",
+      "truncated",
+      "shown",
+      "cap",
+      "totalCount"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

changedOutput schema / properties / cap / description

Previous value: -"Page size applied."New value: +"Page size applied (at most 25)."

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `funder_only_for_awards`: funder is set with a vocabulary other than awards. `unknown_funder`: funder (awards) resolves to no Zenodo funder. `result_window_exceeded`: page × size exceeds 10,000. `rate_limited`: Zenodo answered HTTP 429, or this server's shared Zenodo request budget is spent for the current window. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `funder_only_for_awards`: funder is set with a vocabulary other than awards. `unknown_funder`: funder (awards) resolves to no Zenodo funder. `result_window_exceeded`: The page starts past the first 10,000 entries: (page − 1) × size is 10,000 or more, counting a size above 25 as 25. `rate_limited`: Zenodo answered HTTP 429, or this server's shared Zenodo request budget is spent for the current window. Other values are possible when a failure originates below the handler."

changedOutput schema / properties / has_more / description

Previous value: -"True when more pages follow this one."New value: +"True when another page of reachable entries follows."

changedOutput schema / properties / notice / description

Previous value: -"Guidance on empty results, ambiguous funders, or further pages."New value: +"Guidance on empty results, ambiguous funders, the 10,000-entry window, the 25-per-call size cap, or further pages."

addedOutput schema / properties / reachable

Added value: +{
+  "description": "Entries reachable by paging: min(total, 10,000).",
+  "type": "number"
+}

changedOutput schema / properties / size / description

Previous value: -"Page size applied."New value: +"Page size applied: size, or 25 when size asked for more."

changedOutput schema / properties / truncated / description

Previous value: -"True when more entries exist beyond this page."New value: +"True when more reachable entries follow this page."

First observedOct 9, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety and side-effect profile is covered. The description adds the useful workflow fact that entries carry the parameter name their id feeds, but says nothing extra about pagination caps, remote-call behavior, or failure modes. With annotations carrying the safety burden, this is adequate but thin.

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?

Two dense sentences plus a short third, front-loaded with the core purpose and ending with the downstream-consumption note. It packs many vocabulary/id pairs into one sentence, which is efficient though slightly list-heavy.

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?

An output schema exists, so return values need not be explained, and all five parameters are documented in the schema. The description covers purpose, vocabulary scope, search modes, and the link to zenodo_search_records, leaving only minor gaps around result shape and pagination limits.

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 baseline is 3 and the schema already documents query, funder, vocabulary, page and size thoroughly. The description restates vocabulary scoping and funder scoping in prose without adding format or syntax details beyond the schema (e.g. it omits the 25-per-call cap and the 10,000-entry reachability limit).

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

Purpose5/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 ('resolve names to the ids... browse Zenodo's reference vocabularies') and enumerates the five vocabularies with the identifier type each yields. It explicitly ties itself to zenodo_search_records, so an agent can distinguish it from the other lookup/list siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It frames the tool as the prerequisite step for zenodo_search_records ('the ids zenodo_search_records filters on', 'Each entry names the zenodo_search_records parameter its id feeds'), which is clear when-to-use guidance. It stops short of an explicit routing rule or any when-not-to-use statement, so it is strong but not exhaustive.

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

All zenodo-mcp-server tools Inspect

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.