Skip to main content
Glama

Delete Plan

delete_plan

Delete/cancel a community plan through the legacy plan endpoint. Requires confirm set to DELETE_PLAN.

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": {
      "communityObjectId": "<communityObjectId>"
    },
    "name": "delete_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicit confirmation for this write. Pass the exact literal this tool requires (for example DELETE) only after the user approves the action.
communityObjectIdYesNas.com business (community) object ID, as returned by list_businesses or another Nas.com tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / communityObjectId / description
      Added value: +"Nas.com business (community) object ID, as returned by list_businesses or another Nas.com tool."
    • addedInput schema / properties / confirm / description
      Added value: +"Explicit confirmation for this write. Pass the exact literal this tool requires (for example DELETE) only after the user approves the action."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is largely covered. The description adds useful behavior beyond them: an explicit confirmation gate and the fact that it targets a legacy endpoint, which hints at deprecation risk. It does not say whether the cancellation is reversible, what happens to existing subscribers or billing, or what permissions are needed — and the word "Delete" sits in mild tension with destructiveHint=false, though a plan cancellation can plausibly be non-destructive.

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?

Two short sentences that front-load the action and then the hard requirement. There is no filler, and the mandatory confirmation literal is placed where an agent will see it before constructing the call.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation with no output schema, the definition covers action, endpoint lineage, and the confirmation gate. It leaves the agent guessing about effect (is the plan cancelled immediately, scheduled, or permanently removed?), required permissions, and the boundary with cancel_plan, which matters most for a destructive-sounding operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description earns above that: it supplies the exact literal DELETE_PLAN for confirm, correcting the schema's vague generic example of "DELETE". That literal is the difference between a successful and failed call, and it is stated nowhere else.

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?

"Delete/cancel a community plan through the legacy plan endpoint" names a specific verb and resource and even identifies the underlying endpoint generation. It stops short of telling the agent how this differs from the sibling cancel_plan, so an agent still cannot fully disambiguate the two without extra reasoning.

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?

The description states a precondition (confirm must be DELETE_PLAN) but gives no guidance on when to choose this over cancel_plan or change_plan, nor when-not to use it. Given cancel_plan exists in the sibling set with an almost identical surface action, the absence of routing guidance is a real gap.

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