Skip to main content
Glama

Search AOP-Wiki RDF's curated example queries

search_examples
Read-only

Find curated AOP-Wiki RDF SPARQL examples by describing your goal in words, then use returned IDs and descriptions to adapt. Fetch full queries with get_example.

Instructions

Search the curated example SPARQL queries that AOP-Wiki RDF publishes on its endpoint, by words describing what you want (e.g. 'pathways for a gene', 'count by species'). Returns ids and descriptions; fetch the full query with get_example. Adapting a curated example is faster and more reliable than writing a query from scratch.

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": {
      "text": "<text>"
    },
    "name": "search_examples"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 real value beyond that: it discloses that results are ids plus descriptions only, and that a second call to get_example is required to obtain the actual query, which shapes agent behavior in a way the annotations do not.

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?

Three short sentences, front-loaded with what is searched, then return shape, then the workflow rationale. Every sentence earns its place with no restatement of the title or schema.

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?

An output schema exists, so return values need not be explained, yet the description still usefully flags that only ids and descriptions come back. For a one-parameter search tool this is close to complete; only result-count or matching behavior is unaddressed.

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 0% for the single 'text' parameter, so the description must compensate, and it does with concrete query-like examples ('pathways for a gene', 'count by species'). It still doesn't specify matching semantics (keyword vs. substring vs. fuzzy) or whether results are ranked, leaving a small gap.

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 and resource: search curated example SPARQL queries published by AOP-Wiki RDF, by free-text words. It also names the sibling that follows it (get_example) and distinguishes this tool from writing a query from scratch, so an agent can place it in the workflow without opening a schema.

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?

Gives a clear usage condition — adapt a curated example rather than authoring SPARQL from scratch — and an explicit next step (fetch the full query with get_example). It stops short of saying what to do when no example matches (e.g. fall back to run_sparql), which would have made this a 5.

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