Skip to main content
Glama

AutoTasker Hub — China Social Data API

zenodo_search

Zenodo open research records (datasets, software, papers) with DOI and creators. $0.01 USDC.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, but it only adds a price ($0.01 USDC). It does not say whether this is a read-only search, how results are returned, whether pagination applies, or what authentication or rate limits exist. The price is useful context, but many key behavioral traits are absent.

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?

The description is two compact sentences with no filler, and it front-loads the resource type and metadata. However, the second sentence is only a price note, so the structure is efficient but under-informative rather than genuinely well-structured. It avoids verbosity without adding unnecessary detail.

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

Completeness2/5

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

There is no output schema, no annotations, and zero schema description coverage for two parameters. The description omits query semantics, limit behavior, result format, and usage context, which are all necessary for an agent to invoke this search tool reliably. The single useful addition is the price, but that does not fill the completeness gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters, so the description must compensate. It does not explain the required 'query' parameter, its syntax, or what 'limit' controls and its default/maximum. The mention of DOI and creators appears to describe returned records rather than parameter meaning, leaving both inputs undocumented.

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?

The description identifies the source (Zenodo) and content types (datasets, software, papers), plus DOI and creators, but it never explicitly states that this is a search or retrieval operation. The purpose is inferable from the name and resource details, yet the action itself is vague rather than a clear verb-plus-resource statement. It also does not distinguish Zenodo from sibling scholarly search tools like crossref_search or pubmed_search.

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 guidance on when to use this tool versus alternatives such as crossref_search, arxiv_search, or pubmed_search. The description gives no conditions, exclusions, or prerequisites for choosing Zenodo. The agent must infer usage entirely from the name and resource mention.

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.