roadmap-skill

by shiquda

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

create_tag

Creates a new tag in a project. If no color is provided, it generates one deterministically from the tag name.

Instructions

Create a new tag in a project. If color is omitted, it is generated deterministically from tag name.

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": {
      "projectId": "<projectId>",
      "name": "<name>"
    },
    "name": "create_tag"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`color`	No
`projectId`	Yes
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 7, 2026

TDQS

B3.2/5.0

Behavior2/5

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

The description adds one useful behavioral note (deterministic color generation when omitted), but with no annotations, it fails to disclose other important traits such as idempotency, duplicate handling, authentication requirements, or response/error behavior. The burden on the description is high and only partially met.

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 a single concise sentence that front-loads the core action. However, it could have added brief usage guidance without becoming verbose, so it is efficient but slightly under-specified.

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?

For a simple create operation, the description covers the primary action and one behavioral nuance, but it omits return value, error semantics, duplicate-tag behavior, and prerequisites. Without annotations or an output schema, the description is too sparse to fully inform an agent.

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 description coverage is 0%, so the description should compensate by explaining parameters. It only clarifies the 'color' behavior (generated deterministically) but provides no added meaning for 'name', 'projectId', or 'description'. The schema's patterns and defaults are present but the description does not expand on their intent or usage.

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 verb 'Create' and the resource 'tag in a project', which distinguishes it from sibling tools like update_tag, delete_tag, and list_tags. It precisely identifies the tool's core action and scope.

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 phrase 'in a project' gives contextual scope, but there is no explicit guidance on when to use this tool versus alternatives or any exclusions/prerequisites. Usage is implied rather than directly stated.

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