Skip to main content
Glama
JOSETRA44

openalex-mcp

by JOSETRA44

openalex_search_institutions

Find universities, research institutes, and hospitals in OpenAlex. Retrieve their ID, name, country, type, and publication counts. Use the ID to filter works by institution.

Instructions

Search universities, research institutes, hospitals, and other organizations in OpenAlex. Returns the OpenAlex institution ID (needed for work filters), ROR ID, name, country, type, and publication/citation counts. Use the returned 'openalex_id' in openalex_search_works filter: 'institutions.id:{id}'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
per_pageNo
country_codeNo
institution_typeNo
Behavior4/5

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

No annotations provided, so description carries full burden. It describes the tool as a search (read-only) returning specific fields and how to use the ID. It does not mention destructive behavior, rate limits, or authentication, but these are not critical for a search tool.

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?

The description is two sentences, front-loaded with the purpose, and contains no unnecessary words. Every sentence adds value.

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?

The description covers what the tool searches, what it returns, and how to use the result. Without an output schema, it explains return values well. It could mention that country_code and institution_type are filters, but overall it is fairly complete.

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%, and the description does not explain any of the four parameters (query, per_page, country_code, institution_type). It only mentions returned fields, not how to use the inputs. The description adds no value beyond the schema.

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?

The description clearly states the verb 'Search' and the resource 'universities, research institutes, hospitals, and other organizations in OpenAlex.' It lists returned fields and how to use the OpenAlex ID, distinguishing it from sibling tools that search works, authors, or sources.

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?

The description provides explicit guidance: 'Use the returned openalex_id in openalex_search_works filter'. It implies this tool is for finding institution IDs before filtering works, but does not explicitly state when not to use it or mention alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JOSETRA44/openalex-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server