Skip to main content
Glama
Sign In
mesa-clm

mesa-clm

by idss-mesa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mesa_ols_get_term

Retrieve the full OLS record for a single ontology term by IRI, including label, CURIE, synonyms, definition, and parent/child terms.

Instructions

Get the full record (label, CURIE, synonyms, definition, parents/children) for a single OLS term by IRI.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ontology_id": "<ontology_id>",
      "iri": "<iri>"
    },
    "name": "mesa_ols_get_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
iriYesFull term IRI, e.g. 'http://purl.obolibrary.org/obo/ENVO_00000428'.
ontology_idYesOntology identifier (e.g. 'envo').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the response payload contents (label, CURIE, synonyms, definition, parents/children), which is the most valuable thing here given there is no output schema, but it says nothing about error behavior for an unknown IRI, required permissions, or rate limits.

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 front-loaded sentence with zero filler; the resource and lookup key come first and the returned fields follow as a compact parenthetical.

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?

For a two-parameter read tool with no output schema, listing the returned fields compensates well for the absent return-value documentation. The remaining gap is behavioral (error handling, permissions), which matters slightly more because there are no annotations to fall back on.

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

Parameters3/5

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

Schema description coverage is 100%, with the iri parameter documented including a concrete example, so the schema already does the heavy lifting. The description only restates 'by IRI' and adds no format, casing, or ontology_id/iri relationship detail beyond 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?

Specific verb (get) plus resource (single OLS term) and it enumerates the returned record fields (label, CURIE, synonyms, definition, parents/children). It is clearly distinguishable from search-style siblings, but it never names mesa_ols_search_terms or mesa_ols_get_term_hierarchy, so differentiation is left to inference.

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?

Usage is only implied: 'by IRI' signals that this is a direct lookup when the identifier is already known, which contrasts loosely with mesa_ols_search_terms. There is no explicit when-to-use/when-not statement, no guidance on where to obtain the IRI, and no mention of the hierarchy sibling that also returns parents/children.

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

Deploy Server

Other Tools