Skip to main content
Glama

Resolve a AOP-Wiki RDF entity

resolve_entity
Read-only

Look up canonical IRIs for AOP-Wiki entities from names or identifiers before running SPARQL queries. Avoid hand-building IRIs and reduce query errors.

Instructions

Look up the real IRIs of AOP-Wiki RDF entities from a name or identifier. Call this before writing any query that mentions a specific entity; never build these IRIs by hand. Kinds:

  • aop: an AOP by number ('AOP 1', '1') or title fragment ('liver fibrosis')

  • key_event: a key event by number ('KE 142') or title fragment ('hyperplasia'); also MIEs and AOs

  • ker: a key event relationship by number ('KER 158') or by a fragment of its upstream or downstream KE title

  • stressor: a stressor by number ('Stressor 50'), CAS number ('83-79-4') or name fragment ('rotenone')

  • gene: an HGNC gene by symbol ('TP53') or HGNC number; returns how many KEs are linked to it species (optional, Latin name such as 'Homo sapiens') narrows kinds that have a species.

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": {
      "kind": "<kind>",
      "term": "<term>"
    },
    "name": "resolve_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
termYes
speciesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds useful behavior beyond that: per-kind acceptable input forms, that gene lookups also return a KE link count, and that species narrows only species-bearing kinds. It does not say what happens on ambiguous or zero matches, which would have closed the remaining gap.

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?

Front-loaded with the imperative and the must-call constraint, then a tight bullet list where every line maps a `kind` value to its accepted term formats. No filler or restated title content.

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?

With only 3 parameters and an output schema present, return-value explanation is rightly omitted, and all inputs are documented. The one omission is any guidance on ambiguous terms or not-found results, which matters for a fuzzy name-fragment resolver feeding into SPARQL.

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

Parameters5/5

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

Schema description coverage is 0% and `kind` has no enum, so the description carries the entire burden — and it does: it enumerates all five kinds and gives concrete accepted formats per kind ('AOP 1', 'KE 142', 'KER 158', '83-79-4', 'TP53'). It also clarifies that `species` is optional and Latin-name formatted, adding meaning nowhere present in the schema.

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?

States a specific verb+resource: 'Look up the real IRIs of AOP-Wiki RDF entities from a name or identifier.' It also implicitly separates itself from run_sparql by positioning itself as the prerequisite step before writing a query, so an agent can tell the two apart without inspecting schemas.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use rule ('Call this before writing any query that mentions a specific entity') plus a prohibition ('never build these IRIs by hand'), which is precisely the decision boundary that selects this tool over run_sparql or search_examples.

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