Tolk2Go Interpreter Booking

Search available interpreters

tolk2go_interpreting_search_availability

Read-onlyIdempotent

No key needed. Search interpreters for one assignment with the same filters and results as the tolk2go.com search page. Returns interpreter IDs, ratings and prices (excl. and incl. VAT) plus paging. Search again immediately before tolk2go_interpreting_create_booking so the IDs and prices are current.

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_pair_id": "<language_pair_id>",
      "situation_id": "<situation_id>",
      "start": "<start>",
      "end": "<end>",
      "type": "<type>"
    },
    "name": "tolk2go_interpreting_search_availability"
  }
}

Input Schema

Name	Required	Description
`end`	Yes	End, ISO-8601
`lat`	No	Latitude of the on-site address; required for type address
`lng`	No	Longitude of the on-site address; required for type address
`lang`	No	Locale for names, e.g. nl, en, de or fr (default nl)
`sf_r`	No	Minimum rating in stars
`sf_s`	No	Sort (default relevance)
`type`	Yes	phone = remote by phone or video; address = on site
`limit`	No
`sf_pb`	No	Only interpreters with a profile text
`sf_pm`	No	Minimum price in EUR incl. VAT
`sf_pp`	No	Only interpreters with a profile picture
`sf_px`	No	Maximum price in EUR incl. VAT
`start`	Yes	Start, ISO-8601 with offset or UTC, e.g. 2026-11-20T09:00:00.000Z
`offset`	No	next_offset from the previous result while has_more is true
`examCodeId`	No	Item code from tolk2go_interpreting_list_catalog (e.g. VEE-IT); required for catalogue situations such as CBR, which also need type address with the exam location's lat and lng and end = start + the item's duration_minutes
`with_audio`	No	Only interpreters with a voice recording
`situation_id`	Yes	ID or slug from tolk2go_interpreting_list_situations
`language_pair_id`	Yes	ID or slug from tolk2go_interpreting_list_language_pairs
`qualification_nodes`	No	IDs from tolk2go_interpreting_list_qualifications; an interpreter matches any of them

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

changedInput schema / properties / examCodeId / description

Previous value: -"Catalogue (exam) code, only for catalogue situations such as CBR"New value: +"Item code from tolk2go_interpreting_list_catalog (e.g. VEE-IT); required for catalogue situations such as CBR, which also need type address with the exam location's lat and lng and end = start + the item's duration_minutes"

AddedNov 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so safety needs no restating. The description adds genuinely new context: no API key required, the return payload covers IDs, ratings, prices excl./incl. VAT, and paging, and results go stale quickly.

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 auth caveat, then purpose, then workflow rule. The clause about matching the website's filters and results is slightly promotional but still orients the reader.

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?

With 19 parameters and no output schema, the description still covers the essentials an agent needs: return fields, paging existence, and the freshness requirement before booking. Edge cases such as empty results or error conditions are not addressed, but nothing critical is missing for correct invocation.

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 description coverage is 95%, so nearly every parameter is already documented, including the examCodeId dependency chain and offset paging. The description adds no per-parameter meaning beyond the vague "same filters as the tolk2go.com search page," so baseline 3 applies.

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?

States a specific verb and resource ("Search interpreters") scoped to "one assignment," and anchors it to the public search page so the agent knows this is availability search rather than a catalogue listing. That cleanly separates it from the list_* siblings such as list_catalog and list_situations.

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?

Gives a concrete sequencing rule: re-run the search immediately before tolk2go_interpreting_create_booking so IDs and prices stay current. It does not say when to prefer preview_selection or select_interpreter over this tool, so the alternative-choice guidance is only partial.

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

All Tolk2Go Interpreter Booking tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.