Skip to main content
Glama

Coline

Delete a task view

delete_task_view
DestructiveIdempotent

Moves a view to the trash, where it can be restored.

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": {
      "workspace": "<workspace>",
      "viewId": "<viewId>"
    },
    "name": "delete_task_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds genuinely new information: the deletion is recoverable because the view goes to the trash. That materially changes how an agent should reason about a destructive-marked tool, though it says nothing about permission requirements or side effects on view layout.

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?

A single sentence with zero filler, and the most decision-relevant fact (trash/restorable) is front and center.

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?

An output schema exists and annotations cover the safety profile, so the short description is defensible for a two-parameter tool. However, with an undocumented viewId and no usage guidance, an agent still lacks enough to select this over sibling delete operations confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: the workspace parameter is documented in the schema with a pointer to workspaces.list, but viewId has no description in either schema or description text. The description contributes nothing about accepted identifier formats or scope.

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?

States a specific verb and resource (moves a view to trash) and adds the crucial qualifier that it is a soft delete. It doesn't explicitly distinguish itself from sibling delete tools or update_task_view, but the operation is unambiguous.

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 when-to-use context, no prerequisites (e.g., required permissions or whether the caller must own the view), and no mention of alternatives such as archiving or update_task_view. The agent is left to infer all routing decisions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources