killbottleneck-mcp

Official

Overview Schema Source Related Servers Discussions Admin

get_map

Read a map as an indented tree with node IDs, statuses, deadlines, and owners, including your access level; use it before modifying any map you have not yet read.

Instructions

Read one map as an indented tree with node ids, statuses ([✓] done, [~] in progress, [ ] todo), deadlines and owners. The header shows the key's access level (owner/edit = full write; work and read = only the status of the key owner's own nodes, like ticking off in the app). Always call this before modifying a map you have not read yet.

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": {
      "map_id": "<map_id>"
    },
    "name": "get_map"
  }
}

Input Schema

Name	Required	Description	Default
`map_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.33.2-betaAug 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses the returned status glyph legend, the access-level header, and the crucial permission nuance that work/read keys only expose the key owner's own node statuses. It does not cover error cases, size limits, or what happens with an inaccessible map_id, so it is strong but not exhaustive.

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?

Three sentences, front-loaded with what is returned, followed by the access semantics and the calling precondition. The parenthetical legend is dense but every element earns its place; there is no filler.

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

Completeness5/5

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

For a one-parameter read tool with no output schema and no annotations, the description supplies the return shape, the status legend, permission behavior, and a usage precondition. Nothing an agent needs in order to call it correctly is missing beyond the map_id format detail.

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 documents nothing (0% coverage) for the single map_id parameter. The description only implies that a map is identified by a key ('the key's access level'), but never says whether map_id is that key, an id, or a slug, so an agent must guess the expected format.

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?

States a specific verb and resource ('Read one map') and immediately characterizes the result as an indented tree with node ids, statuses, deadlines and owners. This is specific enough to separate it from list_maps or get_page without consulting a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition: 'Always call this before modifying a map you have not read yet,' which effectively routes the agent away from blind updates. It stops short of naming the write siblings (update_map, add_nodes, update_node) directly, so the alternative is implied rather than stated.

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