Skip to main content
Glama

Aidoptio: AI adoption catalog, estimates and advisor tools

Prepare an Aidoptio request for the person to send

prepare_intake_link
Read-onlyIdempotent

Returns a link to the Aidoptio contact form (English or Dutch) that fills in the chosen offer, optionally the route of estimate_engagement, a plan hash from plan_vendor_evaluation, benchmark_readiness, ai_act_triage or ai_literacy_scan, and three preferred intake moments. The link carries no name, e-mail or other personal data: the person opens it, adds their own details, checks everything and presses Send (with moments: Confirm these moments, through the booking path without any third-party calendar). This tool sends nothing, books nothing and stores nothing; Aidoptio only receives the request after that click. Also returns the exact message text the form will show.

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": {
      "service": "<service>"
    },
    "name": "prepare_intake_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the returned text: en (English, default) or nl (Dutch).en
routeNoOptional route of offers (must contain service), as given to estimate_engagement.
slotsNoExactly 3 preferred moments for the free 30-minute intake, each {date: YYYY-MM-DD, part: morning (9-12) or afternoon (13-17)}, on different business days or parts, from tomorrow up to 60 days ahead, Europe/Amsterdam time. Optional; ask the person, never guess. The person sees them filled in and confirms them on the site; nothing is booked by this tool.
serviceYesOffer id the request is about, e.g. "readiness-sprint".
plan_hashNoOptional 64-character hash from the result of plan_tool (for plan_vendor_evaluation: preregistration.method_hash). Needs plan_tool.
plan_toolNoThe tool that produced plan_hash. Needs plan_hash.

Output Schema

NameRequiredDescriptionDefault
urlYes
langYes
sentYes
bannerYes
storedYes
prefillYes
nothing_storedYes
what_the_person_doesYes
personal_data_in_linkYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, yet the description still adds substantive behavior: the link carries no name, e-mail or other personal data, nothing is sent, booked or stored, and Aidoptio receives the request only after the human clicks Send. It also discloses the side-channel behavior around moments ('Confirm these moments, through the booking path without any third-party calendar') and that the exact message text the form will show is returned. This is context beyond what annotations expose.

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?

Two sentences, front-loaded with what is returned and what it carries, followed by the no-PII/no-write guarantee. The parenthetical about the booking path is slightly dense, but every clause conveys a distinct and useful fact; nothing is filler.

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

Completeness5/5

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

For a six-parameter composition tool with an output schema, the description covers the important agent-facing gaps: data privacy, absence of side effects, the human confirmation step, and the upstream tools feeding route and plan_hash. Return values need not be explained because an output schema exists, and the one return detail mentioned (exact message text) is a useful supplement rather than a substitution.

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 description coverage is 100%, so the baseline would be 3, but the description adds relational meaning the schema cannot: route is 'as given to estimate_engagement', plan_hash is the result of one of four named planning tools, and slots must be asked of the person rather than guessed. This provenance information helps an agent wire parameters to upstream tool outputs, though the date-window and format details largely restate the schema.

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 first sentence gives a specific verb and object ('Returns a link to the Aidoptio contact form') and enumerates exactly what the link is composed from: the chosen offer, optional route, plan hash and three intake moments. This is clearly the 'compose a hand-off link' tool rather than a planning or evaluation tool, so it is distinguishable from siblings such as plan_vendor_evaluation or estimate_engagement at a glance.

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 description establishes the usage context firmly: the tool only prepares a link, the person opens it and clicks Send, and moments are confirmed through the booking path. Preconditions are stated implicitly through the linked source tools ('a plan hash from plan_vendor_evaluation, benchmark_readiness, ai_act_triage or ai_literacy_scan') and via the schema note that plan_hash needs plan_tool. It stops short of an explicit 'use X instead when Y' routing statement, which keeps it from a 5.

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