Skip to main content
Glama

Translation coverage

verbaly_status
Read-only

Reports translation coverage per locale as read-only counts: total messages, translated, machine drafts awaiting review, broken, and outdated, without changing project files.

Instructions

Translation coverage of the Verbaly project as numbers per locale: total messages, translated, machine translations awaiting review (drafts), broken, and translations written for an older source text (outdated). It scans the source like verbaly_extract but writes nothing. Read-only. For the entries behind the numbers, use verbaly_missing (what is missing or broken) or verbaly_drafts (each draft with its source text).

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": "verbaly_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNoProject root holding verbaly.config (defaults to the server working directory)

Output Schema

NameRequiredDescriptionDefault
sourceYesSource locale
localesYes
messagesYesMessages the project has, source catalog plus code
stateProblemNoThe state file could not be read, so drafts and outdated are counted as zero

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description's "writes nothing. Read-only" largely restates that. It does add one piece of non-annotation context — that it scans the source like verbaly_extract — which tells the agent the result reflects a fresh scan of the project rather than a cache. Beyond that it offers no cost, performance, or failure-mode context, so with annotations already covering the safety profile this sits at a solid but not rich 3.

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?

Three sentences, front-loaded with the metric definition, then behavior, then sibling routing — a sensible order with little waste. The standalone "Read-only." fragment is slightly redundant given "writes nothing" and the readOnlyHint annotation, a minor trim opportunity.

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

Completeness5/5

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

For a single-optional-parameter read-only reporting tool with an output schema that documents return shape, the description supplies everything needed: what is counted, that it scans rather than writes, and where to go for the underlying entries. Nothing an agent needs in order to call it correctly is missing.

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?

There is a single optional `root` parameter with 100% schema description coverage, so the schema already explains it fully. The description never mentions scoping, defaults, or multi-project behavior, adding no meaning beyond the structured field. Per the high-coverage baseline, 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ("Translation coverage of the Verbaly project as numbers per locale") and enumerates exactly what is counted: total messages, translated, drafts, broken, outdated. The closing sentence distinguishes it from verbaly_missing and verbaly_drafts, so an agent can pick the right tool without opening any schema.

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

Usage Guidelines5/5

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

It states the selection rule explicitly: use this for aggregate numbers, and use verbaly_missing (missing/broken entries) or verbaly_drafts (individual drafts with source text) when you need the entries behind the numbers. That is a direct when-to-use-this and when-to-use-an-alternative mapping.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.