Skip to main content
Glama

Aidoptio: AI adoption catalog, estimates and advisor tools

Get one Aidoptio service or product

get_service
Read-onlyIdempotent

Returns the full record of one service or product: price, duration, deliverables, summary and EN/NL URLs. Accepts the catalog id (e.g. "readiness-sprint", "agentops-setup", "fractional-caio", "eu-compliant-rag") or the last part of its URL (e.g. "agentops", "interim-chief-ai-officer"). Call get_catalog with section=services to list the ids.

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_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAlias of slug.
langNoLanguage of the returned text: en (English) or nl (Dutch). Omit to get both.
slugNoCatalog id or URL slug of the service or product.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 real context beyond them: the exact payload shape returned and the fact that both EN and NL URLs come back. It omits error/not-found behavior, which keeps it below a 5.

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 sentences, zero filler: return contents first, accepted identifier forms second, discovery path last. The front-loading is correct for an agent deciding whether this is the right tool.

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 compensates by listing the fields returned, and it explains the dual id/slug identifier convention that a caller could otherwise get wrong. The only gap is the absence of failure behavior when an id does not resolve, which matters for a lookup 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 both id and slug are already documented, including that id is an alias of slug and that omitting lang returns both languages. The description reinforces the id/slug aliasing with concrete examples ('readiness-sprint' vs 'agentops'), which is mildly useful but largely restates 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?

States a specific verb and resource ('Returns the full record of one service or product') and immediately enumerates the returned fields (price, duration, deliverables, summary, EN/NL URLs). The final sentence names the sibling get_catalog and its role, so an agent can distinguish lookup-by-id from catalog listing without opening either schema.

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?

Explicitly routes the agent to get_catalog with section=services to discover ids before calling this tool, which is the main precondition for use. It does not state what to do when an id is unknown or invalid, so it falls short of full when/when-not coverage, but the primary alternative is named.

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