Skip to main content
Glama
Sign In
become-human

become-human

by 201Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_map

Retrieves a project's idea map and open items so you can review current scope and unresolved decisions.

Instructions

Full idea map of a project, plus what is still open.

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

Input Schema

NameRequiredDescriptionDefault
projectYesWorking folder name or short topic name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does disclose the returned content: the full map plus open items. However, it omits read-only confirmation, output format/size, and any access requirements, leaving clear gaps.

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?

It is a single front-loaded sentence with no redundant wording. Every phrase contributes to scope: full map and still-open items.

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 one-parameter read tool with no output schema, the description gives useful high-level return content but lacks output structure and usage context. It is adequate but not fully complete.

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 single project parameter is fully documented in the schema, and the description adds no meaning beyond 'of a project'. This matches the baseline of 3 when schema coverage is 100%.

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 states a specific retrieval: a full idea map of a project plus what remains open. The resource and scope are clear, though it does not explicitly name sibling alternatives such as map_add or map_resolve.

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?

Usage is implied—review a project's complete map and unresolved items—but there is no explicit when-to-use, when-not-to-use, or routing to alternatives. The agent must infer this from the stated purpose.

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