Skip to main content
Glama

robot_query

Execute SPARQL queries on OWL ontologies. Supports ASK, SELECT, and CONSTRUCT queries, returning results in CSV or RDF format.

Instructions

Execute SPARQL queries against an ontology.

Use query for pairs of query-file and output-file (e.g. ["cell_part.sparql", "results/cell_part.csv"]). Use queries with output_dir for batch execution. Use update for SPARQL UPDATE operations that modify the ontology.

Query types: ASK (true/false), SELECT (tabular CSV), CONSTRUCT (RDF). Use tdb for large ontologies to use disk-backed storage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputNo
outputNo
queryNo
queriesNo
output_dirNo
updateNo
use_graphsNo
tdbNo
formatNo
working_directoryNo
catalogNo
prefixesNo
add_prefixNo
noprefixesNo
verboseNo
strictNo
xml_entitiesNo
extra_argsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided, so description must carry burden. Mentions query types and storage option (tdb). Missing details on whether queries are read-only unless 'update' is used, and what side effects occur for UPDATE (e.g., irreversible).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is relatively concise (three sentences) and front-loads the purpose. Could be more structured (e.g., bullet list of modes), but current format is clear and efficient.

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

Completeness2/5

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

Given 18 parameters, no annotations, and an output schema (not described), the description lacks details on return values and output format. It mentions file output (CSV, RDF) but no structure. Incomplete for a query tool where output interpretation is crucial.

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?

18 parameters with 0% schema description coverage; description explains only the main mode parameters (query, queries, output_dir, update, tdb) but not others like input, output, prefixes, extra_args, etc. Insufficient detail for an agent to correctly set all parameters.

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?

Description explicitly states the tool executes SPARQL queries against an ontology, and distinguishes it from sibling tools like robot_reason or robot_convert by focusing on querying. The main modes (query, queries, update) are clearly listed.

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?

Provides guidance on when to use each mode: `query` for file pairs, `queries` with `output_dir` for batch, `update` for modifications. Does not explicitly state when not to use, but differentiation from siblings is implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/musen-lab/robot-tool-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server