Skip to main content
Glama

eVerbary Certified Translations

List interpreter request options

interpreter_options
Read-onlyIdempotent

The values request_interpreter accepts: interpreter languages, appointment settings and the types under each, formats (video platforms, phone, in person) and durations - the same lists as the interpreter request form on www.everbary.com.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds useful behavioral context by disclosing that the returned lists mirror a public form on www.everbary.com, implying static reference data, and it names the categories of values returned in lieu of an output schema.

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 sentence that front-loads the core fact (which tool's values these are) and then enumerates the categories. The parenthetical about video/phone/in-person formats is a minor redundancy but still informative; slightly long for one sentence but no filler.

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 no output schema, the description covers what an agent needs: what the tool returns (languages, appointment settings and types, formats, durations) and where those lists come from. The only gap is the precise shape/grouping of the response, which is a minor omission at this complexity.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline for a no-param tool is 4. No misleading parameter claims are present.

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 states a specific resource: the option values accepted by request_interpreter, enumerating the categories (languages, appointment settings and their types, formats, durations). That is enough to tell it apart from request_interpreter itself and from order-related siblings. It stops short of a 5 because it never uses a clear verb ('lists/returns') and doesn't clarify the relationship to sibling list_languages, which sounds like it may overlap.

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

Usage Guidelines4/5

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

The phrase 'the values request_interpreter accepts' plus the reference to the interpreter request form makes the use case clear: call this to learn valid inputs before calling request_interpreter. It gives clear context but no explicit when-not guidance or mention of alternatives such as list_languages.

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.