Skip to main content
Glama

openalex

by io.github.pipeworx-io
OverviewAdmin

Search Authors

search_authors
Read-onlyIdempotent

Find researchers by name or institution affiliation. Returns author name, ORCID, institution, publication count, and total citations.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesTotal number of authors 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. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "Yoshua Bengio"
+  },
+  {
+    "limit": 15,
+    "query": "Fei-Fei Li"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "items": {
+        "properties": {
+          "cited_by_count": {
+            "description": "Total citation count",
+            "type": "number"
+          },
+          "display_name": {
+            "description": "Author's display name",
+            "type": "string"
+          },
+          "id": {
+            "description": "OpenAlex author ID",
+            "type": "string"
+          },
+          "institution_country": {
+            "description": "Country code of institution",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "last_known_institution": {
+            "description": "Last known institutional affiliation",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "orcid": {
+            "description": "ORCID identifier",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "top_concepts": {
+            "description": "Top research concepts (up to 5)",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "works_count": {
+            "description": "Number of published works",
+            "type": "number"
+          }
+        },
+        "required": [
+          "id",
+          "display_name",
+          "orcid",
+          "works_count",
+          "cited_by_count",
+          "last_known_institution",
+          "institution_country",
+          "top_concepts"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of authors matching the query",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "results"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "query": "Yoshua Bengio"
-  },
-  {
-    "limit": 15,
-    "query": "Fei-Fei Li"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "results": {
-      "items": {
-        "properties": {
-          "cited_by_count": {
-            "description": "Total citation count",
-            "type": "number"
-          },
-          "display_name": {
-            "description": "Author's display name",
-            "type": "string"
-          },
-          "id": {
-            "description": "OpenAlex author ID",
-            "type": "string"
-          },
-          "institution_country": {
-            "description": "Country code of institution",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "last_known_institution": {
-            "description": "Last known institutional affiliation",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "orcid": {
-            "description": "ORCID identifier",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "top_concepts": {
-            "description": "Top research concepts (up to 5)",
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          "works_count": {
-            "description": "Number of published works",
-            "type": "number"
-          }
-        },
-        "required": [
-          "id",
-          "display_name",
-          "orcid",
-          "works_count",
-          "cited_by_count",
-          "last_known_institution",
-          "institution_country",
-          "top_concepts"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "total": {
-      "description": "Total number of authors matching the query",
-      "type": "number"
-    }
-  },
-  "required": [
-    "total",
-    "results"
-  ],
-  "type": "object"
-}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "items": {
+        "properties": {
+          "cited_by_count": {
+            "description": "Total citation count",
+            "type": "number"
+          },
+          "display_name": {
+            "description": "Author's display name",
+            "type": "string"
+          },
+          "id": {
+            "description": "OpenAlex author ID",
+            "type": "string"
+          },
+          "institution_country": {
+            "description": "Country code of institution",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "last_known_institution": {
+            "description": "Last known institutional affiliation",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "orcid": {
+            "description": "ORCID identifier",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "top_concepts": {
+            "description": "Top research concepts (up to 5)",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "works_count": {
+            "description": "Number of published works",
+            "type": "number"
+          }
+        },
+        "required": [
+          "id",
+          "display_name",
+          "orcid",
+          "works_count",
+          "cited_by_count",
+          "last_known_institution",
+          "institution_country",
+          "top_concepts"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of authors matching the query",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "results"
+  ],
+  "type": "object"
+}
  5. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "Yoshua Bengio"
+  },
+  {
+    "limit": 15,
+    "query": "Fei-Fei Li"
+  }
+]
  6. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds value by stating the exact return fields (author name, ORCID, institution, publication count, citations) and broadening the query to institution affiliation, which is not in the parameter schema. However, it doesn't mention pagination or external API quirks beyond what annotations cover.

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, front-loaded with the core action and then a list of return fields. Every sentence earns its place; no redundant phrasing.

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?

Given the simple read-only search tool with a full input schema and output schema, the description adequately covers purpose, search criteria, and return format. The annotations cover safety and open-world aspects, making it complete for an agent to invoke.

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 covers all parameters with descriptions (100% coverage), but the description adds crucial semantics by stating the query can be an institution affiliation, which the schema limits to 'Author name'. This extra meaning goes beyond the baseline.

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 uses a specific verb ('Find') with a clear resource ('researchers') and specifies search criteria ('by name or institution affiliation'). This distinguishes it from sibling tools like search_works and search_institutions.

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

Usage Guidelines3/5

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

The description implies the tool is for author searches but does not explicitly compare it with alternatives or state when to use it instead of a sibling. Context is clear but no exclusion or alternative is mentioned, so it relies on the agent's inference.

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