Skip to main content
Glama

remove_earn_rate

Destructive

Deletes a specified earn rate from a credit card's reward configuration using its rate ID. Use it to remove outdated or incorrect earn rates identified through card details.

Instructions

Delete one earn rate (ids are shown by card_details).

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": {
      "rate_id": "<rate_id>"
    },
    "name": "remove_earn_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
rate_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 agent knows this is an irreversible mutation; the bar is lower. The description adds that exactly one rate is removed per call, which scopes the blast radius, but says nothing about whether the deletion is reversible, what happens if the id is stale, or permission requirements.

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?

A single sentence with the action and the id-provenance hint front-loaded; there is no filler, and the parenthetical is the most valuable piece of information placed immediately where it is needed.

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?

The tool has one required parameter and an output schema, so return values need not be explained, and the safety profile is covered by annotations. Given that low complexity, action, scope, and id source are sufficient for correct invocation; only edge-case behavior on invalid ids is absent.

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 0% — rate_id has only a title, no description — so the description carries the full burden. It compensates by telling the agent where valid ids come from (card_details), which is exactly the missing semantic and prevents the agent from guessing the identifier format.

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?

The description opens with a specific verb and resource ('Delete one earn rate'), which clearly separates it from add_earn_rate and from card/purchase siblings. It stops short of an explicit contrast with any sibling, but the noun phrase is distinctive enough for an agent to disambiguate.

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

Usage Guidelines3/5

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

The parenthetical 'ids are shown by card_details' gives a real prerequisite and points the agent at the tool that supplies the required argument, which is useful routing. It does not state when this tool should be preferred over alternatives or any conditions under which deletion should be avoided, so guidance is implied rather than complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.