Skip to main content
Glama

Maple Minute

Choose a new company name

choose_new_name
Destructive

When a company is waiting_for new_name (its name was refused): send a new word name, or numbered: true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "choose_new_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCompany id like MM-12, from list_companies.
nameNo
endingNoInc.
numberedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds real behavioral context by naming the required precondition state, but it does not say what happens to the refused name, whether the new name is re-validated, or what a failure looks like — meaningful gaps for a destructive mutation.

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

Conciseness4/5

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

A single front-loaded sentence with the condition first and the action second; nothing is wasted. The phrasing 'send a new word name' is slightly cryptic, but the structure is efficient.

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?

For a destructive 4-parameter mutation with 25% schema coverage and no output schema, the description is too thin: it never explains ending, never clarifies what numbered produces, and says nothing about the result or failure modes of the rename.

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?

Schema coverage is only 25% (only id is documented), so the description must compensate. It does explain the two main modes — supply a word via name, or set numbered: true — but leaves the ending parameter (default 'Inc.') and the exact semantics of numbered entirely unexplained.

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?

States a specific action (send a new word name) tied to a precise resource state: a company that is waiting_for new_name because its name was refused. That state gate makes the tool's job distinguishable from siblings like start_company or get_company, though it never names an alternative explicitly.

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

Usage Guidelines4/5

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

Gives a clear triggering condition — use this only when the company is in the waiting_for new_name state after a refusal. It does not state when NOT to use it or what to do if the company is in another state, but the precondition is concrete enough to route correctly.

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.

Resources