Skip to main content
Glama

Plures

Read the team's standards

get_standards
Read-only

Returns what this team wants its agents' work to look like: the standing rules in force and recent examples of what they like and don't. Call it before producing work the team will judge, and follow the rules. Pass category for one kind of work; rules that apply to everything are always included. 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_standards"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoThe kind of work, as the team names it: social, logos, support replies
examplesNoHow many recent examples to include. Default 12

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/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 them: globally applicable rules are always included regardless of category, and the call is 'Free,' which signals no cost/rate-limit concern. It stops short of describing response shape or ordering.

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?

Four short sentences, front-loaded with what is returned, then when to call it, then parameter behavior, then cost. Every sentence carries distinct information and nothing is repeated from the schema.

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?

For a two-parameter read-only lookup with full schema coverage and annotations, the description covers purpose, timing, filtering behavior, and cost. With no output schema, it gives only a conceptual account of the return value rather than its shape, which is the remaining gap.

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 would be 3. The description goes further by explaining the semantic effect of category — it narrows to one kind of work while universal rules are always returned — which the schema alone does not convey. The examples parameter is left to the schema's own default note.

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 names a specific verb and resource: it 'returns' the team's standards, spelled out as 'the standing rules in force and recent examples of what they like and don't.' That is far more concrete than the title alone. It does not, however, contrast itself with nearby tools such as check_against_standards or add_standards_rule, so sibling differentiation is left to inference.

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?

'Call it before producing work the team will judge' gives a clear trigger condition for invocation. There is no explicit when-not guidance and no named alternative for validation-style lookups, which keeps it below a 5.

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.