Search OpenAlex for academic sources—journals, repositories, and conferences—by name. Filter by source type and control page size to locate specific publication venues.
Search OpenAlex for sources: journals, repositories, conferences. Returns the unified envelope (record_type source).
| Name | Required | Description | Default |
|---|---|---|---|
| params | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful extra context by disclosing the unified envelope return shape and the record_type of 'source', which are not visible in the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded: the verb, resource, and scoping entity types appear in the first sentence, and the return-envelope note is a single efficient second sentence with no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the output schema and rich annotations, the description is mostly adequate for a simple search tool. However, it omits guidance on query behavior and pagination, and it only indirectly documents the 'type' filter, leaving some ambiguity for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description needed to compensate for undocumented parameters. It only hints at the 'type' filter by listing journal/repository/conference; it does not explain the required 'query' parameter semantics or the 'page' pagination parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Search'), a specific resource ('OpenAlex sources'), and clarifies the entity types covered: journals, repositories, conferences. This clearly distinguishes it from sibling tools like oa_search_works and oa_search_authors.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The intended domain is clear: use this tool when searching OpenAlex source entities. However, the description does not explicitly say when to prefer this tool over alternatives or provide any exclusion guidance, so usage context is implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.