Skip to main content
Glama
RosenAdvertising

smokeball-mcp

unarchive_matter

Restore an archived matter to active status by providing the matter ID, making it accessible again for management and billing.

Instructions

Unarchive a matter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
matter_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits like side effects, permission requirements, or state changes beyond the basic action. The description fails to compensate for missing annotations.

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?

The description is a single sentence, making it concise. However, it is overly terse and lacks necessary detail, sacrificing clarity for brevity.

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 presence of an output schema (not shown) and one parameter, the description is incomplete. It does not explain what happens after unarchiving, any constraints, or how the tool fits into the broader context of matter management.

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 single parameter 'matter_id' has 0% schema description coverage, and the description adds no additional meaning or constraints. While 'matter_id' is self-explanatory, the description could clarify format or required privileges.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Unarchive a matter' uses a specific verb and resource, clearly indicating the inverse operation of 'archive_matter' among siblings. However, it lacks any additional context about what unarchiving entails.

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 versus alternatives. There is no mention of prerequisites, such as whether the matter must be archived first, or any conditions for invocation.

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