Skip to main content
Glama

OwnYourAgent

Get the Ownership Check (Eigendomscheck)

get_ownership_check
Read-onlyIdempotent

Returns the Ownership Check (Eigendomscheck): a vendor-neutral checklist with fixed IDs to test whether an AI agent is owned by the customer, with any vendor, including OwnYourAgent. Sections: exit (E-01..E-10, before signing), protocol (P-, MCP versions and ownership), data (D-), proofs (A-) and switching (X-); only sections whose guide is published are returned, sectionsPlanned lists all. Each item has the question or item and, where the guide gives them, a good answer, a red flag or a done-when. Licence CC BY 4.0: cite the source URL. Not legal advice.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the returned text: nl (Dutch) or en (English). Omit to get both.
sectionNoOne section, or all (default).all

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
itemsYes
usageYes
licenseYes
purposeYes
versionYes
reviewedYes
sectionsYes
changelogYes
publisherYes
notLegalAdviceYes
sectionsPlannedYes

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), but the description adds real behavioral context: only sections whose guide is published are returned and sectionsPlanned exposes the rest, so an agent knows results may be partial. It also discloses a licensing obligation (CC BY 4.0, cite the source URL) and a 'not legal advice' disclaimer that the annotations cannot convey.

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?

Front-loaded with the resource identity and purpose, then the section inventory, then the conditional-fields caveat and licence. It is a dense single block rather than a list, and the ID-prefix notation (P-, D-, A-, X-) is slightly cryptic, but no sentence is filler.

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 0 required parameters, full schema coverage, an output schema, and rich annotations, the description supplies exactly what is missing: the content model, partial-result behavior via sectionsPlanned, and the licensing/liability caveats. An agent has everything needed to call it and interpret the response correctly.

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 a 3 would be the floor, and the description goes beyond it by mapping section values to meaning — exit as E-01..E-10 before signing, protocol as MCP versions and ownership, proofs as A-, switching as X-. The lang parameter is left entirely to the schema, but the section enum gains genuine interpretive value.

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 Ownership Check (Eigendomscheck)' — and immediately qualifies it as a vendor-neutral, fixed-ID checklist for testing whether an AI agent is owned by the customer. The section taxonomy (exit, protocol, data, proofs, switching) makes it unmistakable against siblings like get_agreement_card_template or get_approach.

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?

Usage context is implied rather than stated: the exit section is flagged as applying 'before signing', which hints at the pre-contract scenario. However, there is no explicit when-to-use/when-not direction and no named alternative among the sibling tools, so the agent must infer routing from the resource names alone.

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