Skip to main content
Glama
jmjeong

Whooing MCP

by jmjeong

whooing_delete_entry

Delete a transaction entry from Whooing using its entry ID. First find the entry ID via whooing_entries.

Instructions

Delete a transaction entry from Whooing. Use whooing_entries to find the entry_id first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entry_idYesEntry ID to delete (from whooing_entries)
section_idNoSection ID. Defaults to WHOOING_SECTION_ID env var.

Implementation Reference

  • Registration of the whooing_delete_entry tool with its input schema and handler via server.registerTool.
    // whooing_delete_entry — Delete an entry via Whooing DELETE API
    server.registerTool(
      "whooing_delete_entry",
      {
        description:
          "Delete a transaction entry from Whooing. " +
          "Use whooing_entries to find the entry_id first.",
        inputSchema: {
          entry_id: z.number().int().describe("Entry ID to delete (from whooing_entries)"),
          section_id: z
            .string()
            .optional()
            .describe("Section ID. Defaults to WHOOING_SECTION_ID env var."),
        },
        annotations: { readOnlyHint: false },
      },
      async (args) => {
        const sectionId = args.section_id ?? client.defaultSectionId;
    
        await client.apiDelete(`entries/${args.entry_id}/${sectionId}.json`);
    
        return {
          content: [{ type: "text", text: `Entry ${args.entry_id} deleted.` }],
        };
      }
    );
  • Input schema for whooing_delete_entry requiring entry_id (int) and optional section_id (string).
    inputSchema: {
      entry_id: z.number().int().describe("Entry ID to delete (from whooing_entries)"),
      section_id: z
        .string()
        .optional()
        .describe("Section ID. Defaults to WHOOING_SECTION_ID env var."),
    },
  • Handler that calls client.apiDelete to delete an entry via the Whooing DELETE API.
    async (args) => {
      const sectionId = args.section_id ?? client.defaultSectionId;
    
      await client.apiDelete(`entries/${args.entry_id}/${sectionId}.json`);
    
      return {
        content: [{ type: "text", text: `Entry ${args.entry_id} deleted.` }],
      };
    }
Behavior4/5

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

The description says 'Delete', which is a mutating operation, consistent with readOnlyHint: false. It does not detail side effects or irreversibility, but for a deletion tool, the behavior is fairly transparent. No contradiction with annotations.

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 with no extraneous information. Every word is necessary and front-loaded with the core action and prerequisite.

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?

Given the tool's simplicity (2 params, no output schema, no nested objects), the description is adequate. It covers the action and prerequisite. Could optionally mention response format, but not required.

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?

Input schema has 100% coverage with descriptions for both parameters. The description adds no new parameter information beyond what schema provides; it only reiterates the prerequisite. Baseline 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?

The description clearly states the tool deletes a transaction entry, with the verb 'Delete' and resource 'transaction entry from Whooing'. It also mentions prerequisite (find entry_id via whooing_entries), distinguishing it from siblings like whooing_add_entry or whooing_update_entry.

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?

Explicitly instructs to use whooing_entries to find the entry_id first, providing clear context for when to use this tool. It does not explicitly mention alternatives or when not to use, but the prerequisite guidance is strong.

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/jmjeong/whooing-mcp'

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