Skip to main content
Glama
Sign In
openalex-mcp

openalex-mcp

by ckgerteis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

oa_search_institutions

Read-onlyIdempotent

Search OpenAlex for institutions by name and country to retrieve institution IDs for filtering work searches.

Instructions

Search OpenAlex for institutions. Returns the unified envelope (record_type institution); useful for finding institution IDs to filter work searches.

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": {
      "params": "<params>"
    },
    "name": "oa_search_institutions"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.0
    • addedInput schema / $defs / InstitutionSearchInput / properties / per_page / description
      Added value: +"Results per page (1-200). OpenAlex charges per call, not per result, so a sweep that will page through results should set 200."
  2. Changed1 schema field changedv2.2.0
    • addedInput schema / $defs / InstitutionSearchInput / properties / query / maxLength
      Added value: +2000
  3. First observedv1.1.0

TDQS

A3.9/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 outside the description. The description adds that results come back in a 'unified envelope' with record_type=institution, which is modest but genuine context about result shape beyond the annotations. It does not mention pagination behavior or the per-call cost model that the schema's per_page field hints at.

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?

Two sentences, no filler, and the purpose-plus-routing information is front-loaded before the return-format detail. Every clause either identifies the tool or tells the agent what to do with its output.

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

Completeness4/5

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

With rich annotations, an output schema, and a single nested params object, the description supplies what is needed to select and call the tool. It is slightly thin on parameter guidance (country_code filtering, the per_page=200 sweep tip lives only in the schema) but nothing essential is missing for correct invocation.

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?

The description says nothing about query, page, per_page, or country_code, so it adds no meaning beyond the input schema. With reported schema description coverage at 0%, the description is expected to compensate for undocumented parameters and does not. Credit is limited to the fact that the underlying schema itself partially describes three of the four fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Search) and resource (institutions in OpenAlex) and immediately positions it against the work-search siblings by saying it is for finding institution IDs to filter work searches. An agent can tell this is the institution counterpart of oa_search_works/oa_search_authors without inspecting any schema.

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

Usage Guidelines4/5

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

"Useful for finding institution IDs to filter work searches" gives a concrete when-to-use scenario tied to a downstream sibling tool. It stops short of an explicit exclusion (e.g. 'do not use this to search works or authors') or a note about when to prefer a direct ID lookup, so it is clear context rather than full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools