Skip to main content
Glama

Prepare a subscription negotiation

prepare_negotiation
Read-onlyIdempotent

Use to keep a service for less: weigh a retention offer the user holds, or ask for one. To cancel, use get_exit_plan. Returns documented offer routes with sources and freshness, the cost comparison (modeled_savings with every term; else savings_estimate under named assumptions and a break-even price) and request/counter/decline scripts. Sends nothing; eligibility is unknown until the vendor confirms. Amounts use the current bill's currency and cadence. Stackcut stores the arguments of tool calls to improve its recommendations (vendor names, prices, seats, features, usage numbers, billing amounts and project descriptions; account keys only as a one-way hash, billing and validation sources not at all; never IP addresses). Tool results are summarized; exit tools log only result counts, qualification flags and public evidence statuses, not answer contents. Don't send personal data or secrets.

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": {
      "service": "<service>"
    },
    "name": "prepare_negotiation"
  }
}

Input Schema

NameRequiredDescriptionDefault
feesNoAll mandatory fees over the comparison period; explicit 0 only if confirmed.
marketNoCountry code, e.g. US
serviceYes
billed_byNo
current_planNo
renewal_dateNo
monthly_spendNoCurrent bill. Despite the legacy property name, specify whether this amount is monthly or annual.
offered_priceNo
renewal_priceNo
comparison_monthsNo
required_featuresNo
offer_duration_monthsNoHow long the offer price lasts
offered_contract_monthsNoContract the offer requires
maximum_commitment_monthsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / offer_duration_months / description
      Added value: +"How long the offer price lasts"
    • addedInput schema / properties / offered_contract_months
      Added value: +{
      +  "description": "Contract the offer requires",
      +  "maximum": 1200,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes beyond them by disclosing that nothing is sent to the vendor, that eligibility can't be known until vendor confirmation, and what the response contains (offer routes with sources and freshness, cost comparison with assumptions and break-even price, scripts). It also spells out data retention and summarization behavior, though the long privacy parentheticals read as server-policy boilerplate rather than tool-specific 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?

The purpose and the sibling exclusion are correctly front-loaded in the first two sentences, but the back half is a dense, parenthetical-heavy privacy disclosure whose length rivals the functional content. It earns some of its place (data handling matters here) but is disproportionate and could be tightened considerably.

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

Completeness4/5

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

With no output schema, the description does the necessary work of explaining that results include offer routes with sources/freshness, a modeled_savings-or-savings_estimate comparison with assumptions and break-even price, and request/counter/decline scripts. The remaining gap is coverage of the unschematized optional inputs, which the description only partly addresses.

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 36% across 14 parameters, and the description compensates only partially: it clarifies that amounts follow the bill's currency and cadence (reinforcing the monthly_spend nested object) and implies what offered_price/offer_duration_months represent via "retention offer." Several parameters — fees, comparison_months, required_features, maximum_commitment_months, renewal_price, billed_by — get no explanation in either place, so the gaps remain.

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?

Opens with a concrete verb and outcome ("keep a service for less") and immediately splits the two supported modes: evaluating a retention offer the user already holds, or requesting one. It explicitly names the sibling it is not (get_exit_plan for cancellation), so the agent can distinguish it without opening a schema.

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

Usage Guidelines5/5

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

States when to use it (retention/negotiation intent) and when not to ("To cancel, use get_exit_plan"), giving a named alternative plus the condition that selects it. It also clarifies the tool has no side effects ("Sends nothing"), which sets expectations about what a call accomplishes.

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.