Skip to main content
Glama
Sign In
tick-mcp

tick-mcp

by KpihX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_tag

Delete a tag and remove it from all associated tasks. Clean up your tag list efficiently.

Instructions

Delete a tag. Removes it from all tasks.

[Category: Tags]  [Auth: V2]
[Related: list_tags, merge_tags]

Args:
    tag_name: The tag name to delete.

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": {
      "tag_name": "<tag_name>"
    },
    "name": "delete_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
tag_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that deletion removes the tag from all tasks, but does not mention irreversibility, authorization requirements, or other side effects beyond the action itself.

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 short with two sentences covering purpose and behavior, plus bracketed metadata. It is efficient but the structure mixes prose and metadata, which could be more organized.

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 simplicity of the tool (1 required parameter, no output schema), the description adequately covers the core purpose and effect. However, it lacks guidance on usage context and prerequisites, leaving gaps for an AI agent's decision-making.

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?

The description for the only parameter 'tag_name' merely restates 'The tag name to delete' without adding any meaning beyond the schema's title. With 0% schema description coverage, the description fails to compensate by providing format constraints or examples.

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 'Delete a tag. Removes it from all tasks.' This specifies the action (delete) and the resource (tag), and the additional effect. It distinguishes from siblings like 'list_tags' and 'merge_tags' by explicitly mentioning related tools.

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 explicit guidance on when to use this tool versus alternatives like 'merge_tags' or 'rename_tag'. The description only lists related tools without providing when-to-use or when-not-to-use context.

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

Deploy Server

Other Tools