Skip to main content
Glama

Aidoptio: AI adoption catalog, estimates and advisor tools

Get the Aidoptio catalog

get_catalog
Read-onlyIdempotent

Returns Aidoptio services (price model and amount in EUR excl. VAT, duration, deliverables), ready-to-deploy products and published articles, with canonical English and Dutch URLs. Filter by section and language; limit caps the items per section (default 50).

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the returned text: en (English) or nl (Dutch). Omit to get both.
limitNoMaximum number of items per section.
sectionNoReturn one section only. Omit for all four.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: the default cap of 50 items per section, that the limit applies per section rather than globally, and that prices are EUR excluding VAT with canonical bilingual URLs.

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?

A single dense sentence with the resource list front-loaded and parameter behavior trailing, with no filler. It is slightly packed with parenthetical detail, but every clause carries information an agent needs.

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 no output schema, the description carries the burden of describing return values, and it does so well: item types, price fields, duration, deliverables and URLs. It does not mention ordering, pagination beyond the per-section cap, or response envelope shape, which are minor residual gaps for a read-only catalog tool.

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 100%, so all three parameters are already documented, including the 'omit to get both' behavior for lang and the default of 50 for limit. The description largely restates these facts rather than adding new semantics, so the 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 (Returns) and enumerates the exact resources returned: services with price model/amount in EUR excl. VAT, duration and deliverables, ready-to-deploy products, and published articles with canonical EN/NL URLs. This is concrete enough that an agent can distinguish it from get_service (single item) and search_articles (search) without opening the schema.

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 description explains how to use the parameters (filter by section and language, limit caps items per section) but never says when to choose this tool over siblings such as get_service or search_articles, nor any when-not condition. Usage is implied by the catalog-listing nature 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