Skip to main content
Glama

list_openalex_topics

OpenAlex: search the topic taxonomy (~4500 topics) to find the right subject term for filtering or recent-work queries.

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

Input Schema

NameRequiredDescriptionDefault
queryYes
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully reveals the taxonomy's scale (~4500 topics) and that this is a lookup/search operation, but it says nothing about matching behavior (fuzzy vs exact), whether results are ranked, or pagination limits beyond max_results. That leaves real behavioral gaps for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the resource and its purpose come first and every clause adds information. Nothing is repeated from the title or schema.

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 no output schema and no annotations, the description should say what a returned topic looks like (ID plus display name) and how to feed it back into a filter. It conveys the tool's role well but omits the return shape and result-usage details that an agent needs to chain it correctly.

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%, so the description must compensate for both parameters and does not. It never explains whether 'query' is a substring, fuzzy, or semantic match, nor what max_results defaults to or caps at. The one hint — that results are subject terms used for filtering — is indirect at best.

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 ('search') plus resource ('topic taxonomy') and even quantifies the corpus at ~4500 topics, so an agent knows exactly what this tool returns. It also names the downstream use (subject term for filtering or recent-work queries). It does not explicitly contrast itself with siblings like list_recent, so it falls short of a 5.

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?

It implies when to use it — when you need the correct subject term before filtering or running recent-work queries — which is genuine context rather than none. However, it names no alternative and gives no exclusion such as 'do not use to retrieve works; use search_openalex_works instead'. Usage is implied, not prescribed.

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.