Skip to main content
Glama

GNU gettext PO message export

bpj_gettext_po_pairs
Read-onlyIdempotent

Serialize singular bilingual messages as GNU gettext PO entries with language and UTF-8 headers.

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>",
      "rows": "<rows>"
    },
    "name": "bpj_gettext_po_pairs"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
rowsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that output carries UTF-8 and language headers, which is useful beyond the annotations, but says nothing about malformed lines, how rows lacking a '|' are treated, or what the returned value actually is.

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?

A single front-loaded sentence with the core action first and the qualifiers after; there is no filler. It is slightly over-compressed, packing headers and encoding into a trailing clause without unpacking them.

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 an export/serialization tool with no output schema and zero schema description coverage, an agent still cannot tell whether the result is a string, a file reference, or how invalid input is handled. Annotations carry the safety side and the format name carries selection, but the input-shape and return-shape gaps remain.

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 coverage is 0% and both parameters are required, so the description has to carry weight; it explains that 'to' becomes the language header and that rows are bilingual pairs, which adds some meaning. But it never restates or clarifies the 'Source|translation' line syntax, delimiter handling, or what the 3500-char row limit implies for large inputs.

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 specific verb (serialize) and resource (GNU gettext PO entries) plus the format-defining detail of language and UTF-8 headers. The named format ('GNU gettext PO') is itself a discriminator against sibling exporters like bpj_tmx_memory_export and bpj_xliff_unit_export, though it never explicitly says 'use this instead of those'.

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

Usage Guidelines3/5

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

Usage is only implied: 'singular bilingual messages' hints that pluralized/plural-form entries are out of scope, which is a real constraint. There is no explicit when-to-use statement and no alternative named among the many sibling export tools, leaving selection to be inferred from the format name 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.