Skip to main content
Glama

Plures

Turn a suggested check on or off

set_check
Idempotent

Turns a check on an app's agent map on (added), dismisses it (dismissed), or puts it back to suggested. Turning one on saves its routing rule, so tasks the agent sends for it follow it; test keys reach no real people. Call get_agent_map first for the check ids. Ask the user before changing one.

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": {
      "check": "<check>",
      "status": "<status>"
    },
    "name": "set_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoThe app id. Default: PLURES_APP, then the default app
checkYesThe check's id, from get_agent_map
statusYesadded turns it on, dismissed hides the suggestion, suggested puts it back

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, it discloses the concrete side effect of the 'added' state (the routing rule is saved and the agent's tasks follow it) and scopes the blast radius (test keys reach no real people). That is real behavioral context that the readOnlyHint=false / openWorldHint=true flags alone do not convey. It does not say what happens to already-routed tasks after a dismissal or what is returned on success.

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?

Three short sentences that are front-loaded with the action and its state mapping, followed by the prerequisite and the confirmation requirement. The parenthetical state mapping is compact and every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter mutation tool with no output schema, the definition covers what each state does, where ids come from, the confirmation policy, and the user-impact scoping. The only gap — return value on success — is minor since idempotentHint already tells the agent repeated calls are safe.

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 goes past the enum text by explaining that 'added' saves the check's routing rule and changes how the agent routes tasks, which the schema's terse 'added turns it on' does not convey. The app parameter's defaulting behavior and the origin of check ids are covered by the schema and the get_agent_map prerequisite respectively.

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 verb and resource (sets a check on an app's agent map) and enumerates the three resulting states (added, dismissed, suggested), so the agent understands the exact effect. It does not name the sibling add_check or clarify how creating a check differs from turning one on, which keeps it from a 5.

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 a clear prerequisite (call get_agent_map first to obtain check ids) and an explicit operator policy (ask the user before changing one). It stops short of naming alternatives such as add_check or explaining when a check should be dismissed rather than turned on.

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.