try

add_tool

Add a new tool/step to a project

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	The unique name of the tool (used as identifier)
`tool_type`	No	The type of tool (step, builtin, tip)	step
`is_enabled`	No	Whether the tool is enabled
`session_id`	Yes	The anonymous session ID
`step_order`	No	The order of this step in the project workflow
`description`	No	Description of what the tool does
`tool_schema`	No	JSON schema for tool parameters
`display_name`	Yes	The human-readable display name of the tool
`project_slug`	Yes	The slug of the project to add the tool to
`response_template`	No	Markdown template for tool response

TDQS

B3.2/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 burden of disclosure. It only states the action without revealing behaviors like validation of unique names, required fields, permission requirements, or what happens on duplicate entries.

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 a single, front-loaded sentence with no wasted words. It conveys the essential purpose efficiently, though the 'tool/step' phrasing is slightly informal.

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 (10 parameters, no output schema, no annotations), the description is insufficient. It does not clarify expected return values, required vs. optional fields, or any operational constraints, leaving the agent without enough context.

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?

The input schema provides descriptions for all 10 parameters (100% coverage), so the description adds no additional parameter meaning. The baseline of 3 applies because the schema handles parameter semantics.

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 action (Add) and the resource (tool/step) within a project. It distinguishes itself from sibling tools like add_data_source and update_tool by focusing on the creation of a tool/step specifically.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as update_tool or delete_tool. There is no mention of prerequisites, side effects, or when not to use it.

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

All try tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0

Disambiguation4/5

Most tools are clearly distinct, targeting specific resources (projects, data sources, tools) and actions (add, create, delete, update). Slight overlap exists between toggle_tool and update_tool, and between add_data_source and add_tool, but descriptions clarify the differences.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case, such as add_data_source, create_project, delete_tool, and reorder_steps. No mixing of conventions or vague verbs.

Tool Count5/5

13 tools is within the ideal range for a project management server. Each tool serves a clear purpose in managing projects, data sources, tools, and sessions, without unnecessary redundancy.

Completeness4/5

Core CRUD operations are covered for projects and tools, with additional operations like reorder and toggle. Minor gaps exist: data sources lack an update operation, and there's no explicit list/get for tools or data sources, but project details likely cover this.

Resources

Need Help?