Skip to main content
Glama

delete-routine

Remove a specific routine by its exact name from the Routine MCP server. Confirms user intent before deletion and verifies the correct routine by referencing the list of all routines.

Instructions

Delete a routine by name. Always confirm with user that they want to delete it. User may supply a name that's not exactly as how it's stored. Use the load-routines tool to get the list of all routines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesExact name of the routine to be deleted.

Implementation Reference

  • src/index.ts:106-127 (registration)
    Registration of the 'delete-routine' MCP tool, including description, input schema, and handler function.
    server.tool(
      "delete-routine",
      "Delete a routine by name. Always confirm with user that they want to delete it. User may supply a name that's not exactly as how it's stored. Use the load-routines tool to get the list of all routines.",
      {
        name: z.string().describe("Exact name of the routine to be deleted.")
      },
      async ({ name }) => {
        await deleteRoutine({
          name,
          filename:routineFilename
        })
    
        return {
          content: [
            {
              type: "text",
              text: `Successfully deleted routine ${name}. Always tell user to refresh their MCP tools.`
            }
          ]
        }
      }
    )
  • Handler function that executes the tool logic: deletes the routine using the imported deleteRoutine helper and returns a success response.
    async ({ name }) => {
      await deleteRoutine({
        name,
        filename:routineFilename
      })
    
      return {
        content: [
          {
            type: "text",
            text: `Successfully deleted routine ${name}. Always tell user to refresh their MCP tools.`
          }
        ]
      }
    }
  • Zod input schema defining the 'name' parameter for the delete-routine tool.
    {
      name: z.string().describe("Exact name of the routine to be deleted.")
    },
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the need for user confirmation and potential name mismatches, adding useful context. However, it lacks details on permissions, error handling, or irreversible effects, leaving gaps 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.

Conciseness4/5

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

The description is front-loaded with the core action ('Delete a routine by name') and efficiently includes essential usage notes in two additional sentences. Each sentence earns its place by providing critical guidance without redundancy or unnecessary elaboration.

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?

Given the tool's destructive nature and lack of annotations or output schema, the description is partially complete. It covers purpose and usage well but misses details on behavioral aspects like confirmation mechanisms, error responses, or side effects, which are important for such an operation.

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 description coverage is 100%, so the schema already documents the 'name' parameter fully. The description adds marginal value by noting that 'User may supply a name that's not exactly as how it's stored,' but this doesn't provide additional syntax or format details beyond the schema's 'Exact name' description.

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 specific action ('Delete') and resource ('a routine by name'), distinguishing it from sibling tools like create-routine, load-routines, and update-routine. It precisely defines what the tool does without being vague or tautological.

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?

The description provides explicit guidance on when to use this tool: 'Always confirm with user that they want to delete it' and 'Use the load-routines tool to get the list of all routines.' It also addresses an alternative (load-routines) for verification, making usage context clear and comprehensive.

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

Related 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/mquan/routine'

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