relm_create_pipeline
Create a pipeline. Optionally provide stages [{key,label}] (defaults to lead/qualified/proposal/won/lost) and is_default.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | ||
| name | No | ||
| stages | No | ||
| is_default | No |
Relm CRM
by com.relmcrm
TDQS
B3.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that stages default to a standard list when not provided, which adds behavioral context beyond the annotations. However, it does not describe return values, error behavior, or any side effects other than creation, and the annotations already indicate it is a write operation.
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 concise and front-loaded, with a single sentence that immediately states the purpose and then adds optional parameter 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?
The tool has no output schema and lacks information about return values or post-conditions. The description covers default stages but omits key/name semantics and any mention of what a successful creation returns, making it incomplete for an agent to fully understand the tool's behavior.
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?
The description explains the 'stages' parameter structure and the 'is_default' boolean, but it does not explain the 'key' and 'name' parameters, leaving half the schema undocumented. With 0% schema description coverage, 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 states 'Create a pipeline' with a specific verb and resource, clearly distinguishing from sibling tools like relm_create_automation or relm_manage_pipeline. The purpose is unambiguous.
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. There is no mention of relm_manage_pipeline for existing pipelines or relm_get_pipeline for retrieving, leaving the agent without decision context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.9/5.0
Disambiguation5/5
Every tool targets a distinct resource-action pair (e.g., create_automation, create_pipeline, create_template), and potential overlaps like batch vs create or log_activity vs create are clearly differentiated in descriptions. No two tools appear to do the same thing.
Naming Consistency5/5
All 41 tools follow the relm_<verb>_<noun> pattern in snake_case, with conventional verbs like create, get, list, delete, manage, and restore. Minor plural/singular differences (list_automations vs get_automation) follow standard resource-naming practices and do not break consistency.
Tool Count2/5
At 41 tools, the set is far beyond the 25+ threshold and feels heavy for an agent to navigate. While the CRM domain is broad, many tools could be consolidated (e.g., generic get/list by resource type) without losing clarity.
Completeness4/5
The tool set covers the full record lifecycle (CRUD, restore, batch, search) plus schema management, pipelines, stages, automations, sequences, templates, webhooks, channels, and usage. However, automations, sequences, and templates lack update operations—requiring delete-and-recreate workarounds—which is a minor but notable gap.