Skip to main content
Glama
Sign In

Tolk2Go Interpreter Booking

by com.tolk2go
OverviewDiscussionsAdmin

List interpreter qualifications

tolk2go_interpreting_list_qualifications
Read-onlyIdempotent

No key needed. List the qualification types the search page filters on (such as Sworn Interpreter) and their providers (such as a national register). Pass the IDs as qualification_nodes to tolk2go_interpreting_search_availability when the customer requires a sworn or otherwise qualified interpreter.

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

Input Schema

NameRequiredDescriptionDefault
langNoLocale for names, e.g. nl, en, de or fr (default nl)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 non-obvious context beyond the annotations: no API key is needed and the returned IDs are the input contract for another tool, which is genuinely useful behavioral information.

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?

Three short sentences, front-loaded with the access fact and the resource, then the key chaining instruction. No filler; every clause either describes what is returned or what to do with it.

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?

There is no output schema, and the description compensates by explaining that the result is qualification types with their providers and IDs. The only minor gap is the exact shape of the returned items, but for a small read-only lookup this is close to complete.

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?

Only one optional parameter (lang) and schema description coverage is 100%, so the schema already documents locale format and default. The description adds nothing about the locale parameter, which is acceptable at this coverage level but leaves the baseline.

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?

Names a specific verb and resource (list qualification types and their providers) and gives concrete examples ('Sworn Interpreter', 'a national register'), which tells an agent exactly what comes back. It is clearly distinguishable from sibling lookups like list_languages or 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 Guidelines5/5

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

Explicitly states the downstream action: pass the returned IDs as qualification_nodes to tolk2go_interpreting_search_availability when the customer requires a sworn or otherwise qualified interpreter. That is a concrete when-to-use rule plus the named alternative/next step.

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 toolsInspect
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.

Resources