Skip to main content
Glama

Plures

Check a draft against the team's standards

check_against_standards
Read-only

Holds a draft up against the team's rules and examples before a person sees it, and says which rules it breaks and why. Send the text, a public https image link, or both. Fix what it reports, then ask a person if the work still needs one. 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": "check_against_standards"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftNoThe text of the draft
categoryNoThe kind of work, if you know the team's name for it. Optional and need not be exact: Plures reads the draft and applies the rules of every category it fits
image_urlNoA public https link to the image: PNG, JPEG, WebP or GIF up to 4 MB

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 and openWorldHint, so safety is covered. The description adds useful context beyond that: the output shape (violated rules with reasons), the fix-then-escalate cycle, and a cost note ('Free'). It still doesn't say how long a check takes or what the report looks like in detail.

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?

Front-loaded with the core purpose on sentence one, then input modes, then the follow-up workflow. Every sentence carries information, though 'ask a person if the work still needs one' is a little vague, and the one-word 'Free.' is efficient but abrupt.

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?

No output schema exists, and the description compensates by saying the result names broken rules and reasons. For a read-only, three-optional-parameter check tool with annotations covering safety, this is close to complete; only the granularity of the returned rule list is left unstated.

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?

At 100% schema coverage, all three parameters are already documented, so the baseline is 3. The description contributes one extra fact the schema alone doesn't make obvious: the inputs combine, since you may send text, an image link, or both, confirming nothing is required. That's marginal added meaning over the 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 action and outcome: holds a draft against the team's rules and examples and reports which rules it breaks and why. It also distinguishes itself from human review by framing itself as a pre-screen 'before a person sees it.' Slightly indirect wording ('holds up against') keeps it from a crisp verb, but the resource and result are unmistakable.

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?

Gives a clear implicit when-to-use: before a person reviews the work. It supplies a workflow — fix what it reports, then escalate to a person 'if the work still needs one' — which points at the human-escalation siblings. It doesn't state a case where this tool should be skipped, but the sequencing guidance is strong.

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.