Skip to main content
Glama

Machine translations awaiting review

verbaly_drafts
Read-only

Every machine translation still waiting for a human, each with the source text and what the provider wrote, so a person can read both and decide. Read-only.

Instructions

Every machine translation still waiting for a human, each with the source text and what the provider wrote, so a person can read both and decide. Read-only. Approving is deliberately not a tool here and never will be: a machine translation is unreviewed by definition, so accepting one is verbaly review --approve, run by a human. For how many drafts each locale has, verbaly_status is enough; verbaly_missing lists them next to the gate.

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_drafts"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNoProject root holding verbaly.config (defaults to the server working directory)
localesNoTarget locales (default: all). One the project does not have is an error

Output Schema

NameRequiredDescriptionDefault
totalYes
entriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.84.0
    • changedInput schema / properties / locales / description
      Previous value: -"Target locales (default: all)"New value: +"Target locales (default: all). One the project does not have is an error"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the restated 'Read-only' adds little. However, the description adds real context beyond the annotations: the shape of what comes back (source and provider text side by side) and the deliberate, permanent absence of an approve action, which prevents an agent from hunting for a write path.

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?

The core content is front-loaded in the first sentence, followed by the read-only note and the routing guidance. The 'and never will be' phrasing is slightly rhetorical, but each sentence still conveys a distinct constraint or alternative.

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?

With only two optional parameters at full schema coverage, an output schema for return values, and annotations covering the safety profile, the description needs only to explain selection and the missing approve path — both of which it does.

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 100%, so root and locales are already documented in the schema, and the description adds no format or default detail beyond mentioning per-locale counts. Baseline 3 applies where the schema carries the parameter burden.

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 opening clause names a specific resource and scope — machine translations still awaiting a human — and says what each item carries (source text plus provider output). An agent can distinguish this from verbaly_missing and verbaly_status without opening a 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 explicitly routes two alternatives: use verbaly_status for per-locale counts and verbaly_missing to see drafts next to the gate. It also states the exclusion — approval is not available as a tool and must be done via the human CLI command — which is exactly the kind of when-not guidance that prevents misuse.

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