killbottleneck-mcp

Official

Overview Schema Source Related Servers Discussions Admin

list_maps

Lists goal maps visible to the key owner—own, team, and shared—with id, title, node count, last update, and access level. Set archived=true to list archived maps instead.

Instructions

List goal maps the key owner can see — own, team and shared maps (id, title, node count, last update, access: owner/edit/work/read). Use archived=true to list archived maps instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_maps"
  }
}

Input Schema

Name	Required	Description	Default
`archived`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.33.2-betaAug 17, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it discloses the visibility scope (own/team/shared) and the access levels returned (owner/edit/work/read), which is useful. It does not state that the operation is read-only, whether results are paginated or ordered, or any permission requirements beyond "the key owner can see".

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?

One sentence establishes what is listed, its scope, and the returned fields; a second short sentence handles the parameter mode. Front-loaded, no filler, and the parenthetical keeps field detail compact.

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

Completeness4/5

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

For a one-optional-parameter list tool with no annotations and no output schema, the description covers purpose, visibility scope, returned fields, and the archived switch. The only real omission is pagination/ordering behavior, which is plausible given the schema exposes no paging parameters.

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?

Schema description coverage is 0%, so the description must compensate, and it does: the single `archived` parameter is explained as switching the listing from active maps to archived maps via `archived=true`. That is the essential semantic an agent needs and it is fully covered.

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?

States a specific verb+resource ("List goal maps") and scopes it to what "the key owner can see — own, team and shared maps", which tells an agent exactly what population comes back. It does not explicitly point at get_map for single-map fetches, but the list/get distinction is legible from the name.

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 second sentence gives a concrete mode switch: "Use archived=true to list archived maps instead", so the agent knows how to reach archived content. It gives no guidance on when to prefer this over siblings such as get_map or the create/update map tools, so the when-to-use coverage is only partial.

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