Skip to main content
Glama

Locale plural category samples

bpj_locale_plural_samples
Read-onlyIdempotent

Group supplied numeric samples by cardinal plural category for the requested locale.

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": {
      "to": "<to>",
      "numbers": "<numbers>"
    },
    "name": "bpj_locale_plural_samples"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
numbersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish that this is a safe, read-only, deterministic operation, so the description need not restate safety. It adds the important behavioral detail that grouping is by cardinal plural category, but it does not describe the output shape, category set, or behavior on invalid locales or malformed numeric samples.

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?

The definition is a single front-loaded sentence with no wasted wording. The key operation and grouping criterion appear immediately.

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

Completeness3/5

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

For a simple two-parameter read-only tool, the description is minimally sufficient to convey the operation. However, with no output schema and zero schema description coverage, it should explain the expected return structure and clarify the ambiguous 'to' parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the full parameter burden. It only loosely implies that 'to' is a locale and that 'numbers' are numeric samples; it does not clarify that 'to' is a target language code or that 'numbers' is a comma-separated string rather than an array.

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 ('Group'), resource ('numeric samples'), and grouping criterion ('cardinal plural category'), scoped to a requested locale. It clearly distinguishes cardinal from ordinal plural handling, though it does not name any sibling tool or contrast itself with one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool, when not to use it, or what alternatives exist. The operation is understandable, but the agent must infer its place from the purpose sentence alone.

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.