Skip to main content
Glama
Sign In
ya-tracker-mcp

ya-tracker-mcp

by imdeniil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_entity_checklist_item

Remove a checklist item from a project, portfolio, or goal by specifying the entity type, entity ID, and item ID.

Instructions

Delete a checklist item from a project, portfolio, or goal.

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": {
      "entity_type": "<entity_type>",
      "entity_id": "<entity_id>",
      "item_id": "<item_id>"
    },
    "name": "delete_entity_checklist_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYesChecklist item ID
entity_idYesEntity ID
entity_typeYes"project", "portfolio", or "goal"

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

B3.3/5.0
Behavior2/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 of behavioral disclosure. It states the action 'Delete' but does not mention whether deletion is permanent, if cascading effects occur, what permissions are required, or how errors are handled. For a destructive operation, this lack of context is a significant gap, resulting in a score of 2.

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?

The description is a single sentence of 11 words, direct and free of fluff. It front-loads the action and scope, making it immediately understandable. Every word earns its place, with no 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 simplicity (3 required params, full schema coverage, and an output schema), the description is minimally viable but lacks guidance on behavioral aspects like permanent deletion and permission requirements. The parameter schema covers the inputs well, but the description does not add enough contextual detail to fully inform the agent, especially considering the sibling tools that add ambiguity.

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?

The schema description coverage is 100%, so the baseline is 3. The description repeats the entity_type values ('project, portfolio, or goal') already present in the schema, adding no new semantic meaning beyond what the structured parameter descriptions provide. It does not explain the relationship between item_id and entity_id, so no bonus is warranted.

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?

The description clearly states the action ('Delete a checklist item') and specifies the applicable scope ('from a project, portfolio, or goal'), which differentiates it from the generic sibling `delete_checklist_item`. It is specific and uses a clear verb+resource+scope pattern, but it does not explicitly name the alternative, so it stops short of a 5.

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 for entity-associated checklist items by naming project, portfolio, and goal. However, it provides no explicit guidance on when to choose this tool over the sibling `delete_checklist_item` or any exclusions. The context is present but not fully spelled out, so it earns a 3 for implied rather than explicit usage.

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