Skip to main content
Glama

Openalex

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "query": "MIT"
-  },
-  {
-    "limit": 10,
-    "query": "Stanford University"
-  }
-]New value: +[
+  {
+    "query": "MIT"
+  },
+  {
+    "limit": 10,
+    "query": "University of Oxford"
+  }
+]
  2. 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"
+}
  3. 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"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "MIT"
+  },
+  {
+    "limit": 10,
+    "query": "Stanford University"
+  }
+]
  5. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the location-search flexibility and the specific return fields, which is useful context but not extensive. No contradictions 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?

A single, well-structured sentence that front-loads the purpose and criteria, then lists the return fields. Every word earns its place; no fluff or redundancy.

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?

Given the low parameter count, presence of an output schema, and annotations covering safety, the description is largely complete. It explains the search capability and return fields. Minor gaps like pagination behavior are not needed given the schema's limit parameter and default.

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?

Schema coverage is 100%, so all parameters are documented. The description adds value by clarifying that the 'query' parameter can accept a location (country code) in addition to a name, which is not stated in the schema. This is a meaningful addition 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?

States a specific verb ('Find'), a precise resource ('academic institutions'), and the two search dimensions (name or location). It also enumerates the returned fields, making the tool's role unambiguous and clearly distinct from sibling tools like search_authors or search_works.

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 implies usage context by specifying search criteria and providing an example (country code). It does not explicitly name alternatives or state when not to use it, but the focus on institutions is clear enough for an agent to route correctly among sibling search tools.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources