Skip to main content
Glama

Plures

Is it working

get_scorecard
Read-only

Returns whether precedents and standards are working for this account: precedent accuracy from spot checks, share of decisions answered by precedent, decisions right the first time, standards false alarms, and the time and cost of a decision. Each number comes with how many decisions it rests on; one marked early is a hint, not a fact. Also shows the precedent settings and any change Plures is suggesting. Read only: a person changes settings and answers suggestions in the dashboard. Free.

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_scorecard"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoOne app's decisions only. Leave out for the whole account

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 readOnlyHint=true, and the description reinforces this without contradicting it, adding that settings changes and suggestion answers happen in the dashboard. It contributes genuine behavior the annotations do not cover: each number reports its own decision sample size, early results are explicitly framed as a hint rather than a fact, and the tool is marked 'Free'. That sample-size and confidence framing is exactly the kind of caveat an agent needs before quoting a metric.

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?

The purpose is front-loaded in the first clause and the metric list is compressed into one sentence, followed by the confidence caveat, the read-only boundary, and cost. Slightly long and list-heavy, but every sentence contributes information rather than filler.

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?

There is no output schema, so the description must carry the return-value burden, and it does: it names the metrics, explains the per-metric sample counts, and notes the response also includes current precedent settings and any suggested change. Formatting details are absent, but for a one-parameter read-only report tool this is close to sufficient.

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 description coverage is 100%, so the single 'app' parameter is already fully documented as restricting to one app's decisions. The description adds only the scoping phrase 'for this account', which is consistent but not additive. Baseline 3 is appropriate when the schema carries the semantics.

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 opening sentence states a specific purpose — a scorecard reporting whether precedents and standards are working for the account — and enumerates the concrete metrics (precedent accuracy, share of decisions answered by precedent, first-time-right rate, false alarms, time and cost). An agent can distinguish this from get_standards or get_audit_report because it is clearly an aggregate health report. It stops short of explicitly contrasting with those siblings, so a 4 rather than 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 Guidelines3/5

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

Usage is implied ('returns whether precedents and standards are working') rather than stated as a when-to-use rule. The line 'a person changes settings and answers suggestions in the dashboard' usefully tells the agent this is not the tool for making changes, which is a real boundary. But no explicit alternative is named for related questions such as reviewing standards themselves or running an audit.

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.