roadmap-skill

by shiquda

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

get_task

Fetch a specific task by project and task IDs to view its details and dependencies.

Instructions

Get a specific task by project ID and task ID

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>",
      "taskId": "<taskId>"
    },
    "name": "get_task"
  }
}

Input Schema

Name	Required	Description	Default
`taskId`	Yes
`projectId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 7, 2026

TDQS

A3.7/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 full responsibility for behavioral disclosure. It only says 'Get', implying a read operation, but does not mention error handling (e.g., no task found), auth requirements, read-only guarantees, or any side effects. This is insufficient transparency.

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 concise sentence that is front-loaded with the purpose (Get a specific task) and then provides the identifiers. Every word is necessary, with no fluff.

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?

For a simple get-by-ID tool, the description covers the key purpose and parameters. However, with no output schema or annotations, it omits details about return value shape, error behaviors, and prerequisites, making it minimally viable but not fully complete.

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

Parameters4/5

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

The schema only specifies types and minLength without descriptions, but the description explains that projectId and taskId are used to identify the specific task, adding meaningful semantics. It maps both parameters clearly, compensating for the 0% schema description coverage.

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 tool's function: retrieving a specific task using project ID and task ID. This distinguishes it from sibling tools like list_tasks (list all tasks) and get_tasks_by_tag (retrieve by tag), and the verb 'Get' precisely indicates the action.

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: call this when you need a single task by its project and task ID. However, it does not explicitly provide when-not-to-use or compare with alternatives, leaving the decision to the agent's inference from the sibling list.

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