Skip to main content
Glama
RosenAdvertising

smokeball-mcp

add_role_to_matter

Assign a role to a legal matter by associating an existing contact, clarifying their relationship (e.g., plaintiff, defendant).

Instructions

Add a role to a matter. contact_id: associate a contact to this role.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
matter_idYes
role_nameYes
contact_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, and the description only mentions 'associate a contact' but lacks details on side effects, idempotency, permissions, or error behavior.

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

Conciseness3/5

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

Very concise but underspecified; could provide more value without becoming verbose.

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?

Despite an output schema, the description lacks context on parameter usage, prerequisites, and differentiation from sibling tools.

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%; only contact_id is partially described ('associate a contact to this role'), while required parameters matter_id and role_name are not explained.

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 verb (Add), resource (role), and target (matter), distinguishing it from siblings like remove_role_from_matter and update_role_on_matter.

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 on when to use this tool vs. alternatives (e.g., add_relationship_to_role) or prerequisites (e.g., matter existence, role definition).

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/RosenAdvertising/smokeball-mcp'

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