Skip to main content
Glama
matthewdtowles

iwantmymtg-mcp

delete_transaction

Delete a specific transaction by ID. Requires API key for authorized removal.

Instructions

Delete a transaction by ID. Requires IWMM_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • Defines the delete_transaction tool with name, description, input schema (id field), and handler that sends a DELETE request to /api/v1/transactions/{id}
    export const deleteTransactionTool = {
      name: "delete_transaction",
      description: "Delete a transaction by ID. Requires IWMM_API_KEY.",
      inputSchema: z.object({ id: z.number().int().min(1) }),
      handler: ({ id }: { id: number }) =>
        apiFetch({ path: `/api/v1/transactions/${id}`, method: "DELETE", authenticated: true }),
    };
  • Input schema for delete_transaction: requires a positive integer 'id' for the transaction to delete
    inputSchema: z.object({ id: z.number().int().min(1) }),
  • deleteTransactionTool is imported from ./transactions.js and registered in the tools array at index position 68
    deleteTransactionTool,
  • Import of deleteTransactionTool from ./transactions.js
    deleteTransactionTool,
Behavior2/5

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

With no annotations, the description must disclose behavior. It mentions auth but does not indicate that deletion is destructive or irreversible, nor any 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences with no wasted words, though could slightly expand without becoming verbose.

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

Completeness2/5

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

Lacks information on return value, permanence, or prerequisites beyond API key. Incomplete given the lack of annotations and output schema.

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?

Schema coverage is 0% and the description adds no meaning to the 'id' parameter. It does not explain that it refers to the transaction ID.

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 explicitly states 'Delete a transaction by ID', providing a clear verb and resource. It distinguishes from sibling tools like record_transaction and update_transaction.

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?

No guidance on when to use this tool versus alternatives. Only states an authentication requirement, not the context for deletion.

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