Skip to main content
Glama

Aidoptio: AI adoption catalog, estimates and advisor tools

Get Aidoptio's vendor relations and independence rules

get_disclosures
Read-onlyIdempotent

Returns Aidoptio's public register of vendor relations (the content of /.well-known/disclosures.json: fees received from vendors, resale, each relation with its category, status and default rule), the six rules of the independence policy in the chosen language, and the URLs of the policy, the machine-readable register and the public method log. Relations without a public name are listed by category only and confirmed per name, in writing, in a proposal. The policy is a draft that has not been legally reviewed yet (see policy_status).

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the returned text: en (English, default) or nl (Dutch).en

Output Schema

NameRequiredDescriptionDefault
urlsYes
rulesYes
reviewedNo
relationsYes
policy_statusNo
policy_versionYes
next_review_dueNo
vendor_fees_receivedYes
resells_models_or_platformsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), yet the description adds real substance beyond them: the register's underlying source file, how unnamed relations are handled (category only, confirmed in writing in a proposal), and that the policy is a draft not yet legally reviewed, pointing to policy_status. These are non-obvious behavioral traits an agent could not get from the structured fields.

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?

Content is front-loaded: the main return payload comes first, caveats and the draft-policy warning follow. The prose is dense but each clause (register content, policy rules, URLs, unnamed-relation handling, draft status) contributes information. A single very long sentence reduces scannability slightly.

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?

An output schema exists, so return values need no explanation, and the description still covers the payload's composition and the important caveats about anonymized relations and unreviewed policy status. The remaining gap is usage guidance — when an agent should reach for this tool over its siblings.

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?

With a single parameter at 100% schema description coverage, the schema already explains lang, its enum and default. The description only echoes this with 'in the chosen language', adding no format or edge-case detail. Baseline 3 applies when the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Returns') and enumerates the exact resources: the vendor-relations register mirroring /.well-known/disclosures.json, the six independence-policy rules, and the URLs of the policy, register and method log. That makes the tool's scope unmistakable. It does not name or contrast any sibling tool, so it stops short of the top score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this tool versus alternatives such as get_catalog or plan_vendor_evaluation, and no preconditions are given. The only contextual remarks ('confirmed per name, in writing, in a proposal' and the draft-policy caveat) describe output behavior, not invocation guidance. An agent must infer that this is a transparency/disclosure lookup.

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