Skip to main content
Glama

Open Graph locale alternates

bpj_og_locale_alternates
Read-onlyIdempotent

Validate language_REGION locale syntax and emit primary and unique alternative Open Graph locale tags.

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": {
      "primary": "<primary>",
      "alternates": "<alternates>"
    },
    "name": "bpj_og_locale_alternates"
  }
}

Input Schema

NameRequiredDescriptionDefault
primaryYes
alternatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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, idempotent operation with no destructive effects. The description adds useful behavior by stating that it validates locale syntax and deduplicates alternates, but it does not explain invalid-input handling, error behavior, or the exact emitted output.

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 description is a single, front-loaded sentence with no redundant wording. Every phrase contributes either the validation action or the output behavior.

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 utility this is only minimally complete. Because there is no output schema, the description should more clearly describe the return shape or invalid-input behavior, rather than only saying it emits locale tags.

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 0%, so the description must carry parameter meaning. It partially does by indicating locale syntax and uniqueness for alternates, but it does not explicitly map behavior to the `primary` and `alternates` parameters or clarify newline-separated input beyond what the schema title implies.

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 pair, "Validate" and "emit," and a clear resource, Open Graph locale tags. It is specific enough to distinguish this utility from unrelated siblings, but it does not explicitly contrast itself with any alternative tool.

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 purpose implies a validation/formatting use case, but the agent must infer the context entirely.

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.