Create a new carrier user by providing their email, phone, first and last name, and company name.
Create a new carrier user
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | Carrier email address | ||
| phone | No | Carrier phone number | |
| firstName | No | First name | |
| lastName | No | Last name | |
| companyName | No | Company name |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Minimal description does not disclose behavioral traits like duplication handling, permissions, or response format; no annotations to supplement.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise at 4 words, no wasted content, though structure is minimal.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Lacks context on side effects, error scenarios, or return values; for a creation tool with 5 parameters, more completeness is needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
All parameters have descriptions in the schema, so the description adds no extra meaning; baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the verb 'Create' and resource 'carrier user', distinguishing it from siblings like 'get_carrier' and 'update_carrier'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives such as 'update_carrier' or 'create_company'; no context provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pollamin/opendock-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server