Skip to main content
Glama
matthewdtowles

iwantmymtg-mcp

delete_price_alert

Remove a price alert by specifying its unique identifier.

Instructions

Delete a price alert by ID. Requires IWMM_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The handler for the delete_price_alert tool. Validates input with zod (requires 'id' string), then calls apiFetch to DELETE /api/v1/price-alerts/:id with authentication.
    export const deleteAlertTool = {
      name: "delete_price_alert",
      description: "Delete a price alert by ID. Requires IWMM_API_KEY.",
      inputSchema: z.object({ id: z.string() }),
      handler: ({ id }: { id: string }) =>
        apiFetch({ path: `/api/v1/price-alerts/${encodeURIComponent(id)}`, method: "DELETE", authenticated: true }),
    };
  • Input schema for delete_price_alert: requires a single 'id' string field.
    inputSchema: z.object({ id: z.string() }),
  • Import of deleteAlertTool from alerts.ts into the central tools registry.
    import {
      listAlertsTool,
      createAlertTool,
      updateAlertTool,
      deleteAlertTool,
    } from "./alerts.js";
  • Registration of deleteAlertTool in the tools array, making it available via toolsByName lookups.
    export const tools: ToolDefinition[] = [
      // Read-only (no auth)
      searchCardsTool,
      getCardTool,
      getCardPricesTool,
      getCardPriceHistoryTool,
      searchSetsTool,
      getSetTool,
      listSetCardsTool,
      getSealedProductsTool,
      // Inventory (auth)
      listInventoryTool,
      getInventoryQuantitiesTool,
      addInventoryTool,
      updateInventoryTool,
      removeInventoryTool,
      // Transactions (auth)
      listTransactionsTool,
      recordTransactionTool,
      updateTransactionTool,
      deleteTransactionTool,
      getCostBasisTool,
      // Portfolio (auth; most are Premium-gated)
      getPortfolioSummaryTool,
      getPortfolioHistoryTool,
      getCardPerformanceTool,
      getCashFlowTool,
      getRealizedGainsTool,
      getPortfolioBreakdownTool,
      refreshPortfolioTool,
      // Price alerts (auth)
      listAlertsTool,
      createAlertTool,
      updateAlertTool,
      deleteAlertTool,
  • toolsByName maps tool names (including 'delete_price_alert') to their definitions for MCP call routing.
    export const toolsByName: Record<string, ToolDefinition> = Object.fromEntries(
      tools.map((t) => [t.name, t]),
    );
Behavior3/5

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

Mentions required API key, but no annotations provided. Doesn't state that deletion is irreversible or other side effects.

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?

Two sentences, front-loaded with action, no superfluous content.

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?

Adequate for a simple delete: action, parameter, precondition. No output schema needed, but missing return confirmation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Parameter 'id' has no description in schema and no additional meaning from the tool description. 0% schema coverage not compensated.

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?

Clear verb 'Delete' and resource 'price alert by ID'. Distinct from siblings like create_price_alert and update_price_alert.

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?

Only notes API key requirement. No guidance on when to use vs alternatives (e.g., update_price_alert) or when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/matthewdtowles/iwantmymtg-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server