Skip to main content
Glama

eVerbary Certified Translations

List languages and per-page prices

list_languages
Read-onlyIdempotent

The languages eVerbary translates, with the codes the other tools take, the per-page price beside English and beside another language (surcharge flag). Expedited Plus (same day) covers every pair.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description adds substantive return context: translated languages, codes, per-page prices beside English and another language, a surcharge flag, and same-day Expedited Plus coverage. It does not address authentication or response shape, but for a zero-param lookup the disclosure is meaningful beyond the annotations.

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?

Two sentences, front-loaded with the resource and the most important payload details. The second sentence adds a relevant coverage note without waste; the phrasing is dense but earns its space.

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

Completeness4/5

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

For a zero-parameter, read-only lookup with annotations covering safety, the description is largely sufficient: it identifies the languages, codes, pricing bases, surcharge flag, and expedited coverage. It could be more complete by naming the price currency or clarifying whether the list is exhaustive, but the core needed to call it is present.

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

Parameters4/5

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

There are no input parameters, so the schema is empty and the baseline applies. The description does not need to define parameters, and it stays focused on what the tool returns.

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 the specific resource — the languages eVerbary translates — and the payload: language codes, per-page prices beside English and another language, and a surcharge flag. It does not explicitly contrast with a sibling, but the function is unmistakable for a zero-parameter catalog lookup.

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?

It implies usage by saying the listed codes are 'the codes the other tools take,' which tells an agent to consult it before calling tools that need a language code. However, there is no explicit when-to-use statement, no when-not guidance, and no named alternative.

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.