Skip to main content
Glama

Plures

Send an agent map to Plures

submit_agent_map

Uploads the map you made with get_mapping_guide: nodes, edges and checkpoints with drafted checks. Never include source code, secrets or customer data. If Plures names a problem, fix it and send again.

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": "<map>"
    },
    "name": "submit_agent_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoThe app id, like support-agent. Default: the PLURES_APP environment variable, then the account's default app
mapYesThe agent map, as the guide describes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the agent knows this is a non-idempotent external write. The description adds genuinely useful behavioral context beyond that: a hard content-prohibition list (no source code, secrets, or customer data) and the fact that submission can be rejected with named problems requiring a fix-and-resubmit cycle. It does not describe what a successful submission returns or whether resubmission creates a new version, leaving a gap for a non-idempotent write.

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?

Three compact sentences with zero filler, front-loading the action and its provenance before the safety constraint and the retry loop. The prose is slightly telegraphic ('If Plures names a problem') but nothing is wasted.

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?

With no output schema, the description carries the burden of explaining the response loop, and it does so at a high level by describing the rejection/remediation cycle. The nested map object adds complexity that the description only gestures at ('as the guide describes'), but the prerequisite tool reference supplies that depth elsewhere.

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?

Schema coverage is 100%, so both parameters are already documented by the schema, including the app-id defaulting chain to PLURES_APP. The description reinforces the map's internal shape (nodes/edges/checkpoints) but adds no semantics for the app parameter or the source/commit fields. Baseline 3 is appropriate.

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 concrete verb and resource — 'Uploads the map' — and enumerates the payload contents (nodes, edges, checkpoints with drafted checks), which lets an agent distinguish this write path from the read-oriented sibling get_agent_map. It stops short of naming that sibling explicitly, so the differentiation is inferred from verb direction rather than stated.

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?

Establishes a clear prerequisite chain by tying submission to output from get_mapping_guide, and gives an explicit retry rule: if the service reports a problem, fix and resend. No exclusions or alternative-target guidance (e.g., when to use add_check instead of folding a check into the map) are given, so it is clear context without full when/when-not coverage.

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.