Skip to main content
Glama

Plures

Tell the next map where else to look

set_map_focus
Idempotent

Sets an app's Map also note: the parts of the app the next map should look at too, even if they seem low risk (like refund emails, account deletion, the nightly payout job). get_mapping_guide and npx plures map include it. Send an empty string to clear it.

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": {
      "focus": "<focus>"
    },
    "name": "set_map_focus"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoThe app id. Default: PLURES_APP, then the default app
focusYesWhere to look, in plain words

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, idempotent, open-world write, so the safety profile is covered. The description adds real context beyond that: it names the consumers that pick the value up (get_mapping_guide, npx plures map) and discloses the empty-string reset behavior. It stops short of saying whether the value replaces or appends prior focus, or whether it persists per app vs per map.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the lead sentence is a run-on broken by a missing punctuation boundary ('Map also note:'), which buries the core action behind garbled phrasing. The examples and clearing rule are useful and earn their place; the framing does not.

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 two-parameter setter with no output schema, the description covers what is stored, why it matters, who consumes it, and how to clear it — enough to call correctly. Remaining gaps (replace-vs-merge semantics, failure modes) are minor for this complexity.

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 coverage is 100%, so the baseline is 3, but the description adds semantics the schema lacks: the empty string is a documented reset sentinel for 'focus', and the examples define what kind of content belongs in the field. The 'app' parameter is left entirely to the schema, which is acceptable given full coverage.

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?

The first sentence is garbled — "Sets an app's Map also note:" — so the verb-resource pairing must be reconstructed from the title and the trailing text rather than read cleanly. Once decoded, the tool sets a 'focus' hint that steers what the next generated map inspects, which is specific enough to act on. The broken syntax keeps it below a clear 4.

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?

It gives concrete when-to-use guidance with illustrative examples (refund emails, account deletion, the nightly payout job) and the qualifying condition 'even if they seem low risk.' It also states the clearing case: send an empty string. It does not distinguish this from siblings like add_check or set_check, so no exclusion guidance is present.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.