Skip to main content
Glama

Change Plan

change_plan

Change a community plan. Requires confirm set to CHANGE_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>",
      "priceId": "<priceId>"
    },
    "name": "change_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.
priceIdYesPlan price ID returned unchanged by get_onboarding_plan_options or the plan price tools.
discountCodeNo
communityObjectIdYesNas.com business (community) object ID, as returned by list_businesses or another Nas.com tool.
communityReferralCodeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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."
    • addedInput schema / properties / priceId / description
      Added value: +"Plan price ID returned unchanged by get_onboarding_plan_options or the plan price tools."
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish write, non-destructive, closed-world behavior, and the description adds a genuine behavioral gate: the confirm=CHANGE_PLAN requirement. However, for a billing-plan mutation it says nothing about whether the change is immediate or scheduled, what happens to proration or existing discounts, or whether it is reversible.

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?

Two short sentences, front-loaded with the action and followed by the hard precondition; no filler. It is efficient but so terse that it omits information the agent needs, which is under-specification rather than verbosity.

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?

This is a 5-parameter mutation tool with no output schema and only partial parameter documentation. The description covers the confirmation gate but leaves the effect of the change (timing, billing impact, interaction with discountCode/communityReferralCode) entirely unaddressed.

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 60%, and the description usefully pins the exact confirm literal to CHANGE_PLAN, correcting the schema's generic "DELETE" example. It adds nothing about priceId, discountCode, or communityReferralCode, so the lower-coverage parameters remain unexplained beyond their schema text.

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?

"Change a community plan" gives a clear verb plus resource, so the agent knows this mutates an existing community's plan. It does not differentiate from nearby siblings such as change_plan_tier, revoke_plan_change, or cancel_plan, so an agent cannot tell from the description alone which one applies.

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 only guidance is a precondition (confirm must be CHANGE_PLAN), not a when-to-use rule. There is no statement of when to prefer this over change_plan_tier, revoke_plan_change, or cancel_plan, nor any exclusion of cases where it should not be called.

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