Skip to main content
Glama
Sign In
Taskmaster

Taskmaster

by eyaltoledano
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

use_tag

Switch task operation contexts by specifying a tag name with Task Master’s tool, enabling focused management of tasks within AI-driven development projects.

Instructions

Switch to a different tag context for task operations

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": {
      "name": "<name>",
      "projectRoot": "<projectRoot>"
    },
    "name": "use_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoPath to the tasks file (default: tasks/tasks.json)
nameYesName of the tag to switch to
projectRootYesThe directory of the project. Must be an absolute path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions switching context but doesn't explain what this entails—whether it's a temporary change, affects other operations, has side effects, or requires specific permissions. This leaves significant gaps in understanding the tool's behavior.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of context-switching operations and the lack of annotations and output schema, the description is insufficient. It doesn't clarify what 'tag context' means, how it impacts task operations, or what the expected outcome is, leaving critical gaps for an agent to use the tool effectively.

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%, providing clear documentation for all parameters (file, name, projectRoot). The description adds no additional meaning beyond the schema, such as explaining how 'name' relates to tags or the implications of switching context. This meets the baseline for high schema coverage.

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 ('Switch to') and the resource ('tag context for task operations'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_tags' or 'rename_tag' in terms of functionality, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'list_tags' or 'add_tag', nor does it mention any prerequisites or exclusions. It lacks context for decision-making, leaving the agent to infer usage from the name alone.

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

Related Tools