Skip to main content
Glama

Plan een terugbelmoment met Taklo

plan_terugbelmoment

Vraag aan dat Taklo iemand terugbelt. Het verzoek komt direct als terugbelverzoek in de Taklo-inbox binnen (dezelfde route als het terugbelformulier op taklo.nl) en de aanvrager krijgt een ontvangstbevestiging per e-mail. Er wordt niet automatisch gebeld: een mens belt terug op het opgegeven nummer.

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": {
      "naam": "<naam>",
      "email": "<email>",
      "telefoon": "<telefoon>",
      "voorkeursmoment": "<voorkeursmoment>"
    },
    "name": "plan_terugbelmoment"
  }
}

Input Schema

NameRequiredDescriptionDefault
naamYes
emailYesE-mailadres van de aanvrager; hierop komt de ontvangstbevestiging binnen.
redenNo
telefoonYes
voorkeursmomentYesBijv. "morgenochtend" of "vrijdag na 14:00"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / email / pattern
      Added value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. Changed2 schema fields changed
    • addedInput schema / properties / email
      Added value: +{
      +  "description": "E-mailadres van de aanvrager; hierop komt de ontvangstbevestiging binnen.",
      +  "format": "email",
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "naam",
      -  "telefoon",
      -  "voorkeursmoment"
      -]New value: +[
      +  "naam",
      +  "email",
      +  "telefoon",
      +  "voorkeursmoment"
      +]
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: a request lands in the Taklo inbox, the requester receives a confirmation e-mail, and no call happens automatically — a human calls back later. That async/notification side effect is valuable. It doesn't warn that repeated submissions are not deduplicated (idempotentHint=false), which would be the remaining gap.

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 short sentences, front-loaded with the action, then the mechanism, then the important caveat that no automatic call occurs. No filler, though the taklo.nl form reference is slightly incidental.

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

Completeness3/5

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

Covers the effect on the requester (e-mail confirmation) but says nothing about what the tool returns to the agent (success/ID/error) despite having no output schema. Combined with untouched parameters (naam, reden), the definition is adequate but leaves real gaps.

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

Parameters2/5

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

Schema description coverage is only 40% (naam, telefoon, reden undocumented in the schema), so the description needs to compensate. It only indirectly touches telefon ('opgegeven nummer') and e-mail (confirmation address); it never mentions naam or the optional reden field, so an agent gets no guidance on those inputs.

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 concrete verb+resource: submit a callback request so Taklo calls the requester back. It also explains the concrete backend route (arrives in the Taklo inbox, same path as the taklo.nl callback form), which clearly separates it from the other Taklo tools (info, pricing, connections, trial).

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?

The opening "Vraag aan dat Taklo iemand terugbelt" implies the situation (user wants to be called back), but there is no explicit when-to-use / when-not-to-use framing and no reference to alternatives among the sibling tools. Usage is inferable rather than stated.

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.

Resources