Skip to main content
Glama

template_delete

DestructiveIdempotent

Remove task templates from the Saga MCP project tracker to maintain a clean, organized database structure for AI agents managing projects and tasks.

Instructions

Delete a task template.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTemplate ID

Implementation Reference

  • The handler function that executes the deletion of a template from the database.
    function handleTemplateDelete(args: Record<string, unknown>) {
      const db = getDb();
      const id = args.id as number;
    
      const template = db.prepare('SELECT * FROM templates WHERE id = ?').get(id) as Record<string, unknown> | undefined;
      if (!template) throw new Error(`Template ${id} not found`);
    
      db.prepare('DELETE FROM templates WHERE id = ?').run(id);
      logActivity(db, 'template', id, 'deleted', null, null, null,
        `Template '${template.name}' deleted`);
    
      return { message: `Template '${template.name}' deleted` };
    }
  • The schema definition for the template_delete tool.
      name: 'template_delete',
      description: 'Delete a task template.',
      annotations: { title: 'Delete Template', readOnlyHint: false, destructiveHint: true, idempotentHint: true, openWorldHint: false },
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'integer', description: 'Template ID' },
        },
        required: ['id'],
      },
    },
  • Registration of the template_delete handler in the exports map.
    template_delete: handleTemplateDelete,
Behavior4/5

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

Annotations already indicate destructiveHint=true and idempotentHint=true, which the description doesn't repeat. However, it adds the specific context of deleting a 'task template,' which helps clarify the scope beyond what annotations provide. No contradictions with annotations exist.

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 a single, direct sentence with zero wasted words. It's front-loaded with the key action and resource, making it highly efficient and easy to parse.

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

Completeness3/5

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

For a destructive tool with one parameter and no output schema, the description is minimal but functional. It states what the tool does, but lacks details on error handling, confirmation requirements, or post-deletion effects, which could be helpful given the destructive nature.

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?

The input schema has 100% description coverage, with the 'id' parameter documented as 'Template ID.' The description doesn't add any extra meaning about parameters, such as format or sourcing details, but the schema adequately covers the semantics, meeting the baseline for high coverage.

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 clearly states the action ('Delete') and resource ('a task template'), making the purpose immediately understandable. It doesn't explicitly distinguish from sibling tools like 'template_list' or 'template_create', but the verb 'Delete' is sufficiently specific for this context.

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 is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing the template ID), exclusions, or related tools like 'template_list' for finding IDs or 'note_delete' for similar operations on different resources.

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/spranab/saga-mcp'

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