Skip to main content
Glama
Sign In

LLM Pricing

by io.github.skakumanu
OverviewDiscussionsAdmin

delete_price_alert

Delete a registered price-change alert by its ID. Operator only: needs the server operator's key (MCP_API_KEY) on the MCP connection (x-api-key or Authorization: Bearer); any other caller, including the chat agent and the local STDIO server, gets error_code operator_key_required. To view or delete an alert you registered yourself, use manage_price_alert with the alert_token from registration.

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": {
      "alert_id": "<alert_id>"
    },
    "name": "delete_price_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
alert_idYesThe ID of the alert to delete (from list_price_alerts or register_price_alert)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the exact authentication requirement, accepted header forms, and the error code for unauthorized callers. It does not explicitly state that deletion is permanent or irreversible, which is the main remaining behavioral gap for a destructive operation.

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?

The description is front-loaded with the core action, then adds the crucial operator restriction and the alternative routing in later sentences. Every sentence contributes distinct information, and there is no redundant restatement of the tool name.

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?

For a one-parameter destructive tool with no annotations or output schema, the description covers the main operational requirements: authentication, caller restrictions, error behavior, and routing to manage_price_alert. It could be slightly more complete by stating that deletion is permanent, but otherwise it gives an agent enough to invoke the tool correctly.

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 100%, so the alert_id parameter and its source are already documented by the input schema. The description says deletion is by ID but adds no further syntax, constraints, or format details beyond what the schema provides, so the baseline of 3 is appropriate.

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?

States a specific verb and resource: delete a registered price-change alert by ID. It also distinguishes the operator-only path from the self-service path via manage_price_alert, so an agent can tell when this tool applies rather than guessing from the name alone.

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?

Explicitly names the required operator key and says any other caller, including the chat agent and local STDIO server, will receive operator_key_required. It also names the correct alternative for self-registered alerts: manage_price_alert with the registration alert_token.

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

All LLM Pricing toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources