Skip to main content
Glama
Sign In

FlowCastle

by ai.flowcastle
OverviewDiscussionsAdmin

delete_task

DestructiveIdempotent

Delete one CRM task. Leads parked on it come back to Waiting on us. The task disappears from CRM → Tasks; to finish a task instead, use update_task with status "done".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "taskId": "<taskId>"
    },
    "name": "delete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesRequired. Task id, as returned by list_tasks.
applicationIdNoApplication (workspace) id. Optional: an application-scoped key (app_...) defaults to its own application, but a personal key (usr_...) has no default and omitting it fails with MCP_APPLICATION_REQUIRED. Call list_applications to get the id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover destructiveness and idempotency, but the description adds the non-obvious cascade: "Leads parked on it come back to Waiting on us," which no annotation conveys. It stops short of stating whether deletion is recoverable or what happens to dependent follow-up tasks, leaving a meaningful gap 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.

Conciseness5/5

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

Three short sentences, front-loaded with the action and immediately followed by the side effect and the alternative. Every clause carries information; nothing is redundant with the title or annotations.

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?

For a two-parameter destructive tool with no output schema, it covers action, cascade effect, and the safer alternative. It is slightly incomplete on reversibility and on what happens to records that reference the task (e.g., follow-up tasks), which matters for a delete.

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 coverage is 100% and both parameters (taskId, applicationId) are fully documented in the schema, including the MCP_APPLICATION_REQUIRED failure mode for personal keys. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ("Delete one CRM task") plus the observable effect ("The task disappears from CRM → Tasks"), which no sibling like update_task or list_tasks shares. An agent can distinguish this from the update/complete path without opening a schema.

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?

Explicitly routes the agent away from this tool when the intent is completion: "to finish a task instead, use update_task with status 'done'." That is a named alternative with the condition that selects it, which is exactly the when/when-not guidance expected.

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

All FlowCastle toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources