Skip to main content
Glama

robot_template

Convert CSV or TSV tabular data into OWL ontology format using a template file that defines headers and mapping strings.

Instructions

Convert tabular data (CSV/TSV) into OWL ontology format.

The template file has: row 1 = headers, row 2 = template strings (e.g. ID, LABEL, SC % for subclass), rows 3+ = data. Use merge_before or merge_after to control how template output combines with the input ontology.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputNo
outputNo
templateNo
prefixNo
ontology_iriNo
merge_beforeNo
merge_afterNo
forceNo
errorsNo
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?

With no annotations, the description carries the full burden. It explains the template process but lacks disclosure of side effects (e.g., file overwriting, error behavior) or authorization needs. Adequate but not detailed.

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?

The description is extremely concise—two sentences. The first sentence states the core purpose; the second adds key structural and usage details. No wasted words.

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 the tool's complexity (18 parameters, no schema descriptions), the description is too sparse. It does not cover many crucial parameters or scenarios, even though an output schema exists. Incomplete for effective agent use.

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?

Schema coverage is 0%, so the description must compensate. It only explains two parameters (merge_before, merge_after) and the template structure, leaving 16 other parameters (e.g., input, output, force) undocumented. This is a significant 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?

The description clearly states the tool converts tabular data (CSV/TSV) into OWL ontology format, with a specific verb and resource. This distinguishes it from sibling tools like robot_annotate or robot_convert.

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?

The description explains the template file structure (row1=headers, row2=template strings) and mentions merge_before/merge_after for controlling combination with input ontology. However, it does not explicitly state when to use this tool versus alternatives like robot_convert for other conversions.

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