Skip to main content
Glama

Zenodo Search

zenodo_search
Read-onlyIdempotent

Search Zenodo open-research repository for datasets, publications, software, and other research outputs by keyword query. Filterable by type, community, and sort order (mostrecent/bestmatch/mostviewed); returns metadata, DOI, and file links.

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": {
      "query": "climate change data"
    },
    "name": "zenodo_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sizeNo
sortNomostrecent | bestmatch | mostviewed
typeNodataset | publication | software | presentation | poster | image | video | other
queryYes
communitiesNoComma-sep community ids.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is fully covered structurally. The description adds modest value by saying results include metadata, DOI, and file links, but it omits pagination behavior, default page size, result caps, or rate limits — relevant for an open-world HTTP-backed search.

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 sentences, front-loaded with the verb and corpus, followed by filters and return shape. The clause 'and other research outputs' is slightly redundant with the enumerated types but does signal an open-ended set, so waste is minimal.

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 spelled out, and required-parameter information comes from the schema. However, for a six-parameter paginated search tool, the absence of any pagination or result-volume guidance leaves a meaningful gap for correct invocation.

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 coverage is 50%: sort and type options are already described in the schema, and the description largely restates them (mostrecent/bestmatch/mostviewed, type filtering) rather than adding meaning. It does hint at community filtering, but page and size — the pagination controls — are explained in neither the schema nor the description.

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?

States a concrete verb and resource ('Search Zenodo open-research repository') and enumerates the content types it indexes (datasets, publications, software), so the agent knows what corpus is being queried. It stops short of distinguishing itself by name from siblings like zenodo_record or zenodo_communities, leaving that differentiation to inference.

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?

The phrase 'by keyword query' implies this is the discovery path, but there is no explicit when-to-use guidance, no statement of when to prefer zenodo_record or zenodo_communities, and no prerequisites or exclusions. The filter list describes capability, not the conditions that should select this tool.

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.