Skip to main content
Glama

openalex

by io.github.pipeworx-io
OverviewAdmin

Search Institutions

search_institutions
Read-onlyIdempotent

Find academic institutions by name or location (e.g., country code 'US', 'GB'). Returns institution name, country, type, publication count, and research areas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return (1-25, default 10)
queryYesInstitution name to search for (e.g., "MIT")
_apiKeyNoOpenAlex API key. Optional — Pipeworx supplies one; pass your own to bill your account instead.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesTotal number of institutions matching the query
resultsYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / _apiKey
      Added value: +{
+  "description": "OpenAlex API key. Optional — Pipeworx supplies one; pass your own to bill your account instead.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "items": {
+        "properties": {
+          "cited_by_count": {
+            "description": "Total citation count",
+            "type": "number"
+          },
+          "country_code": {
+            "description": "ISO country code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "display_name": {
+            "description": "Institution name",
+            "type": "string"
+          },
+          "homepage_url": {
+            "description": "Institution homepage URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "OpenAlex institution ID",
+            "type": "string"
+          },
+          "ror": {
+            "description": "Research Organization Registry ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "top_concepts": {
+            "description": "Top research concepts (up to 5)",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "type": {
+            "description": "Institution type",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "works_count": {
+            "description": "Number of works published",
+            "type": "number"
+          }
+        },
+        "required": [
+          "id",
+          "display_name",
+          "ror",
+          "country_code",
+          "type",
+          "works_count",
+          "cited_by_count",
+          "homepage_url",
+          "top_concepts"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of institutions matching the query",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "results"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "MIT"
+  },
+  {
+    "limit": 10,
+    "query": "Stanford University"
+  }
+]
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful behavioral context: query can match by name or country code, and it lists return fields. No contradiction with annotations.

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?

One concise, front-loaded sentence communicates purpose and returns, and the inline country-code example is not verbose. No unnecessary words.

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

Completeness5/5

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

For a simple search tool with full schema coverage, an output schema, and safety annotations, the description is complete. It states what to search, how (name/location), and what results look like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema covers all parameters, but the description adds meaning beyond schema by expanding query to include location/country-code search, while schema only says institution name. This is especially helpful because query is required.

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?

Description names the specific action ('Find academic institutions') and the resource (academic institutions), with search dimensions (name or location). This distinguishes it from sibling search_authors/search_works. The country-code example further clarifies scope.

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?

Clear context for use: when you need to find institutions by name or location. It does not explicitly mention alternatives or exclusions, but the tool's name and description make its primary use obvious.

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

All openalex toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources