Skip to main content
Glama
Sign In
become-human

become-human

by 201Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

map_resolve

Mark a question answered or a next step done for a specific project, keeping the project map accurate for follow-up work.

Instructions

Mark a question answered or a next step done.

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>",
      "id": "<id>"
    },
    "name": "map_resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
projectYesWorking folder name or short topic name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden and does not meet it. It does not say whether the item is deleted, flagged, or archived, whether the call is idempotent, what happens if the id is unknown or already resolved, or whether project scoping is enforced.

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?

A single short sentence with the action front-loaded and no filler. Its brevity is the right shape, though the brevity here reflects under-specification rather than tightness.

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?

A mutation tool with no annotations, no output schema, and an unresolved gap between its name and its description. An agent still lacks the effect of 'resolve', the return value, and the failure modes needed to invoke it safely.

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?

Two required parameters at 50% schema coverage, and the description mentions neither. It never explains that 'id' is the identifier of the map item to resolve, nor that 'project' scopes the lookup to a working folder, leaving the undocumented 'id' parameter with no meaning anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete action ('mark ... answered/done') but never connects it to the map abstraction implied by the tool name and by siblings like get_map and map_add. An agent cannot tell from this sentence whether the target is an entry in a map, a task, or a question object, so sibling differentiation is left implicit.

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

Usage Guidelines2/5

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

No guidance on when to call this versus get_map, map_add, or forget, and no prerequisites such as the item having been created first. The only implicit cue is the 'answered/done' framing, which suggests closing an existing item but is never stated as an exclusion.

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