Skip to main content
Glama
Sign In
mesa-clm

mesa-clm

by idss-mesa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mesa_ols_search_terms

Search OLS ontology terms across all ontologies or one, and optionally limit results to descendants of a parent IRI.

Instructions

Search OLS terms across all ontologies or scoped to one. Optionally restrict to descendants of a parent IRI (hierarchy walk).

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": {
      "query": "<query>"
    },
    "name": "mesa_ols_search_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoMax results.
queryYesFree-text search string.
ontology_idNoOptional ontology to restrict the search (e.g. 'envo').
descendants_ofNoOptional parent term IRI. When set together with ``ontology_id``, only descendants of this term are returned (uses the v1-compat ``allChildrenOf`` search).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing beyond the operation itself: no result ordering, ranking, pagination, or the fact that the hierarchy walk requires ontology_id to be meaningful. The one useful behavioral hint ('hierarchy walk') is thin.

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 short sentences, front-loaded with the core operation and followed immediately by the optional narrowing behavior. No filler, no restatement of the tool name.

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 search tool with full schema coverage and no output schema, the description is minimally sufficient to select and call the tool. It is missing return-behavior context (ordering, result shape, default limit semantics) that the absent annotations and output schema leave uncovered.

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%, so the baseline is 3; the schema already documents query, size, ontology_id and descendants_of (including the allChildrenOf compatibility note). The description adds only the 'hierarchy walk' framing and does not clarify the ontology_id + descendants_of interaction beyond what the schema says.

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?

States a specific verb (search) and resource (OLS terms) and adds scope framing ('across all ontologies or scoped to one'), which separates it from sibling readers like mesa_ols_get_term and mesa_ols_get_term_hierarchy. It does not explicitly name those siblings, so it stops short of a 5.

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 when the scoping and descendant options apply, but that is essentially a restatement of the schema parameters rather than independent usage guidance. There is no explicit when-not or pointer to the alternative tools (get_term, get_term_hierarchy) an agent should consider.

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