Skip to main content
Glama

Aidoptio: AI adoption catalog, estimates and advisor tools

Search Aidoptio articles

search_articles
Read-onlyIdempotent

Keyword search over the published Aidoptio articles (titles, excerpts, keywords and tags, English and Dutch). Returns the best matches with title, excerpt, date, category and EN/NL URLs. Please cite the article URL.

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": {
      "query": "<query>"
    },
    "name": "search_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the returned text: en (English) or nl (Dutch). Omit to get both.
limitNoMaximum number of results.
queryYesSearch terms, e.g. "private eval benchmark" or "EU AI Act agents".

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 cover the safety profile (readOnly, idempotent, closed-world, non-destructive), and the description adds real context beyond them: which article fields are matched, that both EN/NL URL variants come back, and that results are ranked 'best matches'. It omits any note on pagination behavior (there is a limit but no offset) or how relevance is computed, which keeps it from 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, front-loaded with the core action and scope, followed by return contents and the citation instruction. Every sentence carries information an agent needs; nothing is redundant.

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 does its job by enumerating returned fields (title, excerpt, date, category, EN/NL URLs), so an agent knows what it gets back. For a simple three-parameter read tool this is nearly complete; only the absence of any note about result paging or total counts leaves a minor gap.

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 earns a bump by clarifying that 'query' is a keyword search over titles, excerpts, keywords and tags rather than full-text semantic search, and by confirming the EN/NL scope that the 'lang' enum selects. It adds no detail on limit behavior, which the schema already documents.

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 ('keyword search') and resource ('published Aidoptio articles'), and narrows scope by naming the fields searched (titles, excerpts, keywords, tags) and the two languages. An agent can immediately tell this is a content-retrieval tool, distinct from siblings like get_catalog or get_service.

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 makes clear this is for keyword lookup against published articles only, and ends with a usage instruction ('Please cite the article URL'). It does not name an alternative tool or state when-not to use it, so it stops short of full routing guidance.

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