Skip to main content
Glama
Sign In

mFlow

by io.m-flow
OverviewDiscussionsAdmin

delete_standalone_attachment

Destructive

Delete an attachment from a standalone task. This cannot be undone.

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>",
      "attachmentId": "<attachmentId>"
    },
    "name": "delete_standalone_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesThe task the attachment belongs to.
attachmentIdYesThe attachment to delete, from list_standalone_attachments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / attachmentId / description
      Added value: +"The attachment to delete, from list_standalone_attachments."
    • addedInput schema / properties / taskId / description
      Added value: +"The task the attachment belongs to."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

While annotations already declare destructiveHint=true and readOnlyHint=false, the description adds the critical detail that the operation cannot be undone. This goes beyond the annotation flags and provides important context about irreversibility.

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 concise sentences with no filler. The essential action and a key warning are front-loaded, making it easy to parse quickly.

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 simple deletion tool with full schema coverage and clear destructive annotations, the description is sufficient. No output schema exists, and it is not necessary to explain return values for a delete operation. The irreversibility warning adds important context.

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%, and both taskId and attachmentId have clear descriptions. The tool description does not add any extra semantic detail beyond what the schema already provides, so the baseline of 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 action (delete), the resource (attachment), and the scope (standalone task). It is distinct from sibling delete tools for comments, labels, projects, etc., making it easy for an agent to select the correct one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage is for standalone tasks, but does not explicitly state when to use this tool over alternatives or when not to use it. There is no mention of non-standalone attachments or other deletion tools, leaving some inference required.

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

All mFlow 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