Skip to main content
Glama

eVerbary Certified Translations

Request an interpreter

request_interpreter
Idempotent

Ask eVerbary for a human interpreter for an appointment, for the user: an asylum or immigration interview, court hearing, attorney meeting, deposition, medical, school or business appointment - in person, by video or by phone. Use it when the user needs an interpreter. Call first with confirm=false and show the preview; then call again with confirm=true and a request_id once the user agrees. eVerbary answers by email with a written quote; the result says what happens next. Nothing is charged by this tool.

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": {
      "language": "<language>",
      "setting": "<setting>",
      "format": "<format>",
      "phone": "<phone>"
    },
    "name": "request_interpreter"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity and state, plus the address or office if known. Required for in_person.
dateNoDate of the appointment, YYYY-MM-DD.
emailNoWhere the quote is emailed. Leave out to use the account's.
phoneYesPhone number eVerbary can call about the request.
formatYesHow the interpreter joins: video, phone or in_person.
confirmNofalse: preview only. true: send the request (after the user agreed to the preview).
detailsNoAnything else the interpreter should know (dialect, who attends, how many people). No identification or case numbers.
settingYesWhat the appointment is: 'Asylum or immigration interview', 'Immigration court hearing', 'Attorney-client meeting', 'Deposition', 'Medical appointment', 'School or IEP meeting', 'Business meeting or conference' or 'Other'.
durationNoExpected length: '1 hour', '2 hours', '3 hours', 'Half day', 'Full day' or 'Not sure yet'.
languageYesThe language the interpreter speaks with the user besides English, e.g. 'Spanish', 'Haitian Creole', 'Dari' (interpreter_options lists them; any other is sent as 'Other').
last_nameNo
first_nameNoFirst name of the person eVerbary answers. Leave out to use the account's.
ok_to_textNoThe person agrees to be texted at that number.
request_idNoRequired with confirm=true: a unique string for this request (e.g. a UUID). Retrying with the same request_id never sends it twice.
start_timeNoStart time with time zone if not obvious, e.g. '9:00 AM'.
organizationNoThe company or organization asking, if not for the person or their family.
video_platformNoFor format=video: the platform, if known.zoom
appointment_typeNoThe type within the setting, e.g. 'Asylum interview', 'Master calendar hearing', 'IEP meeting' (interpreter_options 'types'); anything else is sent as written.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations (which already declare openWorldHint, idempotentHint and non-destructive), it discloses that eVerbary answers by email with a written quote, that the result indicates next steps, and that nothing is charged here. The request_id retry explanation restates the idempotency hint but usefully supplies the mechanism. It stops short of describing response shape or expected turnaround.

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?

It is front-loaded with purpose, then scenario list, then the operating protocol and the cost/response note. Every sentence carries information an agent needs; nothing is redundant.

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 an 18-parameter mutation with no output schema, the description covers the essential operational context: cost, delivery channel of the quote, the idempotent retry rule, and the two-step confirmation. A brief note on what the preview contains or expected response time would make it complete, but nothing critical is missing.

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?

Schema coverage is 94%, so the schema carries the field-level detail and a baseline of 3 would apply. The description adds real value on the two flow-critical parameters by defining the confirm/request_id protocol and the preview-then-send semantics that tie them together.

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 names a specific verb and resource ('Ask eVerbary for a human interpreter for an appointment') and enumerates the covered settings and formats, so an agent can immediately tell this is the booking tool rather than an options or pricing lookup.

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 gives an explicit trigger ('Use it when the user needs an interpreter') and prescribes the exact call sequence: first with confirm=false and show the preview, then with confirm=true plus a request_id once the user agrees. That is a complete when/how protocol with no inference required.

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.