Skip to main content
Glama

Ror

by io.github.pipeworx-io

Search

search
Read-onlyIdempotent

Search the Research Organization Registry (ROR) for universities, research institutes, hospitals, companies, and funders by name or acronym, with optional filters for organization type (education, healthcare, company, government, nonprofit, facility, archive, other) and ISO-3166 alpha-2 country code. Returns each organization ROR id, official and alternate names, country and location, types, and external identifiers. Answers which ROR id belongs to a named research institution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page (default 1)
typeNoeducation | healthcare | company | archive | nonprofit | government | facility | other
queryYese.g. "harvard university"
countryNoISO-3166 alpha-2 country code, e.g. "US"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNoArray of organization records
queryNoQuery parameters used
time_takenNoAPI response time in milliseconds
number_of_resultsNoTotal number of results matching the query

Schema Changelog

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

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "harvard university"
+  },
+  {
+    "country": "US",
+    "page": 1,
+    "query": "Stanford",
+    "type": "education"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Search results from ROR organizations endpoint",
+  "properties": {
+    "items": {
+      "description": "Array of organization records",
+      "items": {
+        "properties": {
+          "acronyms": {
+            "description": "Organization acronyms",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "addresses": {
+            "description": "Organization addresses",
+            "items": {
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "aliases": {
+            "description": "Alternative names",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "country": {
+            "properties": {
+              "country_code": {
+                "type": "string"
+              },
+              "country_name": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "email_address": {
+            "description": "Organization email address if available",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "established": {
+            "description": "Year the organization was established",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "ROR organization ID (URL)",
+            "type": "string"
+          },
+          "ip_addresses": {
+            "description": "Associated IP address ranges",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "links": {
+            "description": "External links",
+            "items": {
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "name": {
+            "description": "Organization name",
+            "type": "string"
+          },
+          "relationships": {
+            "description": "Related organizations",
+            "items": {
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "types": {
+            "description": "Organization types",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "number_of_results": {
+      "description": "Total number of results matching the query",
+      "type": "number"
+    },
+    "query": {
+      "description": "Query parameters used",
+      "type": "object"
+    },
+    "time_taken": {
+      "description": "API response time in milliseconds",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. 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, idempotentHint, and non-destructive behavior. The description adds context about return fields, which is helpful, but it does not disclose pagination limits, result caps, or rate limits. With strong annotations, the additional value is moderate but not exceptional.

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 three sentences, with the core function front-loaded. Each sentence adds distinct value: purpose, output, and use case. There is no verbosity, redundancy, or irrelevant detail.

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 rich input schema (100% coverage) and presence of output schema, the description is largely complete for guiding an agent. It covers what, filters, and result content. Minor gap: no explicit mention of pagination behavior, but the schema's 'page' parameter and examples cover it sufficiently.

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%, providing baseline of 3. The description adds meaning by specifying that 'query' is a name or acronym, which is not explicit in the schema, and it summarizes the type/country filters efficiently. This extra clarity justifies a score above 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 the specific verb 'Search' with a clear resource 'Research Organization Registry (ROR)' and enumerates the types of institutions targeted. It also states the output fields (ROR id, names, country, types, identifiers) and answers a concrete question ('which ROR id belongs to a named research institution'), differentiating it from sibling tools like 'get' or 'entity_profile'.

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 clear context: use this tool to identify a ROR ID for a named institution, with optional filters. However, it does not explicitly mention when not to use it or compare to alternatives, such as 'search_within' or 'get', leaving some ambiguity.

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

All Ror 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.

TDQS

A3.5/5.0
Disambiguation2/5

Several tools have overlapping purposes: ask_pipeworx and ask_pipeworx_beta are currently identical, deep_research overlaps with ask_pipeworx, and discover_tools/suggest_questions both serve a discovery role. The extremely detailed descriptions help, but the boundaries between meta-tools and research tools are genuinely confusing, especially with 34 tools in one namespace.

Naming Consistency2/5

Naming is a mix of bare verbs (get, search, recall), nouns (affiliation, entity_profile, recent_changes), and verb_noun phrases (resolve_entity, compare_entities, validate_claim). Some families are consistent (polymarket_*), but overall there is no uniform convention or prefix scheme, making the set feel arbitrary.

Tool Count2/5

34 tools is well above the 25+ threshold for 'too many.' While the broad data-platform scope explains some of the count, many tools are meta-utilities (feedback, trending, memory, subscription management) and there are near-duplicate variants (three ask_pipeworx forms, six Polymarket tools) that inflate the surface.

Completeness4/5

For a data-research platform the surface is impressively complete: lookup, grounded verification, entity profiles, comparisons, claim checking, subscription lifecycle, memory, and tool discovery are all covered. Minor gaps exist (e.g., no direct general-purpose web fetch, and ROR lacks create/update, which is acceptable for a curated registry), but agents should rarely hit dead ends.

Resources