Skip to main content
Glama

Plures

Get an agent map

get_agent_map
Read-only

Returns an app's agent map from Plures: its checkpoints, which are added, and live numbers for each (checks in 30 days, agreement, how many went to the team).

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": "get_agent_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoThe app id. Default: PLURES_APP, then the default app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered structurally. The description does add payload context beyond the annotations by naming the returned content (checkpoints, added checks, 30-day check counts, agreement, team escalation counts), but it says nothing about data freshness, permissions, or whether the numbers are cached versus live in practice.

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?

One compact sentence that front-loads the verb and resource, then spends its remaining words on the returned fields. Slightly dense parenthetical, but nothing wasted and no repetition of the title.

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?

With no output schema, the description must carry the return shape, and it partially does by listing checkpoints, added checks, and live metrics. It still leaves the exact structure and field naming of those live numbers to discovery, so an agent gets the gist but not the full contract.

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% and the single 'app' parameter is fully documented in the schema, including its default resolution order (PLURES_APP, then the default app). The description adds no parameter meaning beyond that, which is the expected baseline for a fully described one-parameter schema.

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 ("Returns an app's agent map from Plures") and enumerates what the map contains: checkpoints, which checks are added, and live per-check numbers. This is clearly a read of a specific artifact and is distinguishable from siblings like submit_agent_map or get_map_versions, though it never explicitly contrasts itself with get_map_versions.

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 only implied: an agent can infer this is the way to inspect the current agent map, but there is no explicit when-to-use statement, no mention of prerequisites, and no routing to alternatives such as get_map_versions for historical versions or submit_agent_map for writes.

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.