Skip to main content
Glama

get_openalex_trends

OpenAlex: publication-trend analytics for a query — counts grouped by year (default), or by 'institutions.id', 'authorships.author.id', 'open_access.is_oa', 'type', 'language'. Returns aggregate counts only (cheap, no rows).

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": "get_openalex_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
group_byNopublication_year

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose the return shape (aggregate counts, no individual rows) and a cost hint ('cheap'), which is genuinely useful. It says nothing about query syntax expectations, rate limits, result caps, or authentication, all of which matter for an unannotated API-backed tool.

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?

One dense sentence with the primary function front-loaded, followed by grouping options and the output-shape caveat. No filler, though the grouping list makes it slightly scan-heavy at the end.

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?

For a low-complexity two-parameter tool with no output schema, the description covers what is returned and the grouping dimension reasonably well. The main gap is the required query parameter: nothing explains whether it accepts OpenAlex filter syntax, plain keywords, or something else, which is the one thing an agent must get right to call this successfully.

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 0%, so the description must compensate, and it does so well for group_by by enumerating the accepted values (institutions.id, authorships.author.id, open_access.is_oa, type, language) and confirming year as default. It adds nothing about the required 'query' parameter, leaving its syntax and filtering behavior entirely undocumented.

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 names a specific resource and operation: publication-trend analytics for a query, returning counts grouped by year or by a named dimension. It also implicitly separates itself from row-returning siblings via 'Returns aggregate counts only (cheap, no rows)', though it never names a concrete alternative.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the 'cheap, no rows' phrasing signals this is for aggregate trend questions rather than record retrieval, which helps an agent choose against search_openalex_works. There is no explicit when-not-to-use condition and no named alternative tool to route to.

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.