Skip to main content
Glama

Zenodo Communities

zenodo_communities
Read-onlyIdempotent

List or search Zenodo communities (thematic collections of records) by optional keyword query; returns community id, title, description, and record count.

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": "astronomy"
    },
    "name": "zenodo_communities"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sizeNo
queryNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/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 by structured data. The description adds that results are keyword-filterable and enumerates returned fields, but says nothing about pagination behavior, default page size, result caps, or ordering — the operational details that actually matter for an open-world listing call.

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?

A single front-loaded sentence with no filler: purpose first, input mechanism second, return shape last. Efficient, though the return-field enumeration is somewhat wasted effort given a dedicated output schema exists.

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?

With an output schema present, the description need not enumerate return fields, and the core purpose is adequately conveyed. However, for a paginated open-world listing tool with zero schema parameter documentation, the omission of pagination defaults and any hint about result volume leaves a real gap.

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

Parameters2/5

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

Schema description coverage is 0% for three parameters, so the description must carry the burden and largely does not. It clarifies that 'query' is an optional keyword filter, but 'page' and 'size' are never explained — no defaults, ranges, or page-size limits — leaving an agent to guess at pagination semantics.

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 gives a specific verb pair plus the resource ('List or search Zenodo communities') and even glosses the resource as 'thematic collections of records', which tells an agent what a community is. It does not name or contrast any sibling (e.g. community_records or zenodo_search), so disambiguation is left 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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of the clearly adjacent sibling community_records, which an agent could easily confuse with this tool. The phrase 'by optional keyword query' implies all three parameters are optional, but that is the only usage signal present.

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.