Skip to main content
Glama

Aidoptio: AI adoption catalog, estimates and advisor tools

Estimate an Aidoptio engagement

estimate_engagement
Read-onlyIdempotent

Prices a route of 1 to 5 Aidoptio offers with the published amounts only (EUR, excl. VAT): per step the price model (fixed, from, range, on-request, free), amount or bounds, unit and the page URL; the one credit rule the site states (the full Readiness Sprint fee is credited against Pilot to Production when both are in the route, Sprint first); totals per one-time, per month and per year, where max is null when a step has only a starting price or is quoted per scope. Not a quote: the final amount follows from a written proposal. Example: route ["readiness-sprint"] answers "what does a sprint cost". Rule-based, no model, nothing stored.

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": {
      "route": "<route>"
    },
    "name": "estimate_engagement"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the returned text: en (English, default) or nl (Dutch).en
routeYesOffer ids in the order of the steps, 1 to 5 (e.g. ["readiness-sprint", "pilot-to-production"]). Ids: get_catalog (services, their tiers and products).

Output Schema

NameRequiredDescriptionDefault
nextYes
basisYes
routeYes
totalsYes
creditsYes
currencyYes
pricing_pageYes
vat_includedYes
quoted_per_scopeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld=false, so safety is covered; the description adds real behavioral detail beyond that: the single credit rule and its ordering dependency (Sprint first), and that max is null when a step has only a starting price or is quoted per scope. It also discloses 'Rule-based, no model, nothing stored,' which tells the agent results are deterministic and side-effect free.

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?

Front-loaded with purpose and dense with substantive content; the example and the 'Not a quote' caveat both earn their place. The pricing-field enumeration is delivered as one long semicolon-chained sentence, which is harder to parse than a short bulleted structure would be.

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 deterministic pricing calculator with an output schema, this covers what an agent needs: input bounds, ordering, currency and VAT basis, the credit rule, null/max edge cases, and an explicit disclaimer about authoritative pricing. Nothing material is left to inference.

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 100%, so the baseline is 3, but the description adds genuine meaning: route entries are ordered steps (which matters for the credit rule) and the 1-5 bound is stated. It also explains the pricing fields returned per step, going past what the schema documents for the route array.

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 ('Prices a route of 1 to 5 Aidoptio offers') plus a hard scope constraint ('published amounts only (EUR, excl. VAT)'). The closing contrast 'Not a quote' and the get_catalog pointer separate it from the catalog/sibling tools without ambiguity.

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 usage example ('route ["readiness-sprint"] answers "what does a sprint cost"') and states a boundary condition ('Not a quote: the final amount follows from a written proposal'). It does not explicitly name an alternative tool for full proposals, so a 4 rather than 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