Skip to main content
Glama

Plures

Save an example of what the team likes or doesn't

add_standards_example

Saves something the team likes or doesn't, so their agents can take it into account: an image by public https link, or a piece of text, with an optional note on why. Plures describes and tags it.

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": {
      "verdict": "<verdict>"
    },
    "name": "add_standards_example"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoWhat they like or dislike about it, in their words
textNoThe text, when the example is writing
verdictYesWhether the team likes it or not
categoryNoThe kind of work it is an example of
image_urlNoA public https link to the image

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the mutation and open-world annotations, it discloses the downstream effect on the team's agents and the automatic processing whereby Plures describes and tags the example. It does not cover URL-fetch failures or response behavior, but those are secondary omissions for this simple tool.

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?

Two compact sentences front-load the action, purpose, supported content types, and optional rationale. The final statement about Plures adds new processing information without unnecessary wording.

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?

Together with the fully described flat schema and annotations, the description is sufficient for most invocations. Its main gaps are the exact text-versus-image cardinality and the absence of an explicit boundary between saving an example and defining a standards rule.

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 baseline is 3. The description usefully connects the note to the rationale and presents image and text as content options, but largely repeats schema details and does not clarify whether one content field is required or whether both may be supplied.

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 gives a clear action and purpose: save an image or writing example representing a team like or dislike so agents can account for it later. It does not explicitly distinguish these examples from sibling resources such as standards rules.

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 establishes a clear usage context: capture something the team likes or dislikes, with an optional explanation, for future agent guidance. It does not state when a standards rule, check, or another sibling tool would be more appropriate.

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.