Skip to main content
Glama

Get the user's Stackcut savings plan

get_my_plan
Read-onlyIdempotent

Use only when the user gives you a Stackcut agent code (it starts with sca_; they copy it from 'Send to my agent' on stackcut.io). Returns their own savings plan: every subscription with its verdict, the proven saving, the proof (receipts, card charges or a sourced price), steps and checks. Walk them through it from the biggest proven saving down and ask before any cancel, purchase or sign-up. The code is read-only and expires. 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": {
      "code": "<code>"
    },
    "name": "get_my_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYessca_ and 43 letters, digits, - or _; expires in 1-30 days

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / code / description
      Previous value: -"The agent code from stackcut.io, e.g. sca_…"New value: +"sca_ and 43 letters, digits, - or _; expires in 1-30 days"
  2. Changed1 schema field changed
    • addedInput schema / properties / code / maxLength
      Added value: +200
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the code is read-only and expires, explains what the returned plan contains, and adds detailed privacy and logging behavior. It also warns not to send personal data or secrets, which is useful behavioral context for an agent handling the code.

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?

The important selection condition and return contents are front-loaded, and the privacy details are clearly separated. The description is long, but most sentences carry relevant invocation, workflow, or data-handling information rather than filler.

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

Completeness5/5

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

There is no output schema, so the description carries the burden of explaining returns, and it does so by listing the plan contents and the recommended walkthrough. Combined with annotations covering safety and idempotency, it provides enough context to invoke and use the tool correctly.

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?

The schema already defines the code format and expiry, but the description adds provenance and meaning: the code starts with sca_ and is copied from 'Send to my agent' on stackcut.io. It also reinforces that the code is read-only and expires, though it does not add much beyond the schema's syntax constraints.

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?

The description states a specific verb and resource: it returns the user's own savings plan, including every subscription with its verdict, proven saving, proof, steps, and checks. The Stackcut agent code condition and 'their own' scope distinguish it from broader siblings such as audit_stack or get_exit_plan.

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?

It gives an explicit usage gate: 'Use only when the user gives you a Stackcut agent code,' which also implies when not to use it. It adds workflow guidance to walk through savings and ask before cancel/purchase/sign-up, but it does not explicitly name alternative tools for other situations.

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.