Skip to main content
Glama

Ebi Ols

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Term Ancestors

term_ancestors
Read-onlyIdempotent

Transitive ancestors of a term.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iriYes
ontologyYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
_linksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / _embedded
      Removed value: -{
-  "properties": {
-    "ancestors": {
-      "description": "Array of ancestor terms in hierarchy",
-      "items": {
-        "description": "Ancestor term with IRI and label",
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "type": "object"
-}
    • addedOutput schema / properties / _links
      Added value: +{
+  "properties": {
+    "self": {
+      "properties": {
+        "href": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / page
      Added value: +{
+  "properties": {
+    "number": {
+      "type": "number"
+    },
+    "size": {
+      "type": "number"
+    },
+    "totalElements": {
+      "type": "number"
+    },
+    "totalPages": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "iri": "http://www.ebi.ac.uk/efo/EFO_0000408",
+    "ontology": "efo"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Transitive closure of ancestor terms",
+  "properties": {
+    "_embedded": {
+      "properties": {
+        "ancestors": {
+          "description": "Array of ancestor terms in hierarchy",
+          "items": {
+            "description": "Ancestor term with IRI and label",
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the behavioral detail 'transitive', clarifying that all ancestors up the hierarchy are returned rather than just immediate ones. This is a useful addition beyond the annotations, but minimal.

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 sentence with zero wasted words. The core functionality is front-loaded and immediately understandable. No extraneous information is included.

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

Completeness3/5

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

For a simple read-only ontology lookup tool with an output schema present, the description is mostly adequate. It conveys the transitive nature, and the output schema handles return values. However, it lacks any mention of edge cases (e.g., whether the term itself is included) and does not differentiate from sibling tools beyond the direction. It meets the minimum viable level but has clear gaps in usage context.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the burden of explaining parameters. It does not mention 'iri' or 'ontology' at all. While the parameter names are self-explanatory and the schema includes an example, the description fails to provide any additional semantic value, leaving the agent to rely solely on the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Transitive ancestors of a term' clearly indicates the tool returns the transitive (all) ancestors for a given term. It specifies the resource (term) and the operation (returning ancestors), and distinguishes it from sibling term_children by the direction of traversal. However, it could be more explicit about the verb (e.g., 'get' or 'retrieve'), but the intent is clear.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives. It does not mention conditions for selection, exclusions, or reference any sibling tools. The agent is left to infer that it should be used when ancestors are needed, which is not explicit.

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

All Ebi Ols 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