Skip to main content
Glama

Aidoptio: AI adoption catalog, estimates and advisor tools

Check whether a text came from the Aidoptio assistant

verify_ai_text
Read-only

Checks a text against the fingerprints of answers given by the AI assistant on aidoptio.com (AI Act Article 50(2) marking). Returns match (the whole text), partial (some sentences, with counts and dates), none or inactive. It only knows the Aidoptio assistant: "none" says nothing about other AI systems. The text is hashed in memory and never stored. Limit: 20 checks per hour.

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": {
      "text": "<text>"
    },
    "name": "verify_ai_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the returned text: en (English, default) or nl (Dutch).en
textYesThe text to check, as copied.

Output Schema

NameRequiredDescriptionDefault
dateNo
noteYes
datesNo
scopeNo
totalNo
statusYes
matchedNo
meaningYes
check_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing privacy behavior (text hashed in memory, never stored), a concrete rate limit (20 checks per hour), and the four possible verdicts including the ambiguous 'inactive' state. The annotations only declare read-only/non-destructive; the description supplies the operational constraints an agent actually needs.

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?

Four tight sentences, each carrying distinct information: purpose, return states, scope limitation, privacy, and quota. The return-state enumeration briefly overlaps the output schema but earns its place by setting up the important 'none' caveat.

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?

With an output schema present, the description does not need to detail return structure, yet it still covers the interpretive trap ('none' is not proof of human authorship), privacy, and rate limits. Nothing an agent needs to call this correctly or interpret it responsibly is missing.

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 'text' and 'lang' are already documented in the schema. The description reinforces that the text should be the material as copied and that hashing happens in memory, but adds nothing about the lang parameter or length limits, so the baseline of 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 (checks), a specific resource (a text against fingerprints of Aidoptio assistant answers), and names the underlying marking regime (AI Act Article 50(2)). It also draws an explicit boundary: 'It only knows the Aidoptio assistant,' which prevents the agent from confusing it with a general AI-text detector.

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 the tool for checking whether text came from the Aidoptio assistant and warns that 'none' says nothing about other AI systems, which is real usage guidance for interpreting results. It does not explicitly point to a sibling for other verification needs (e.g. verify_report), so it stops short of full when-to-use/when-not routing.

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