Skip to main content
Glama

OwnYourAgent

Compare answer files of the Ownership Check

compare_ownership_checks
Read-onlyIdempotent

Compares two answer files of the Ownership Check (Eigendomscheck) question by question: per ID the answer of every vendor (yes, partial, no or unknown) and whether it has a proof URL, whether the answers differ, a count per vendor, and the sha256 of each file as received (JSON with unescaped slashes and unicode), so the user can show which files were compared. Without "b", the own answers of OwnYourAgent (get_vendor_answers) are the second file, which compares another vendor with OwnYourAgent. At most 8 vendors in total. The server fetches nothing: pass the files themselves. Nothing is stored. It compares self-declarations; it does not certify anyone. Not legal advice.

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": {
      "a": "<a>"
    },
    "name": "compare_ownership_checks"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesAn answer file of the Ownership Check (format ownyouragent-ownership-check-answers, formatVersion 0.1 or 0.2): exported on the guide page, or the result of get_vendor_answers, or a file a vendor publishes at /.well-known/ownership-check-answers.json.
bNoAn answer file of the Ownership Check (format ownyouragent-ownership-check-answers, formatVersion 0.1 or 0.2): exported on the guide page, or the result of get_vendor_answers, or a file a vendor publishes at /.well-known/ownership-check-answers.json.
langNoLanguage of the returned text: nl (Dutch) or en (English). Omit to get both.

Output Schema

NameRequiredDescriptionDefault
noteYes
checkYes
itemsYes
sourcesYes
summaryYes
warningsYes
differingYes

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 declare readOnlyHint/idempotentHint/openWorldHint=false, so safety is covered; the description adds genuinely new behavioral facts: no server-side fetching, nothing is stored, a cap of 8 vendors, and that each file's sha256 is echoed back as received so the user can prove which files were compared. It does not discuss error behavior on mismatched formats or versions, which is the remaining gap.

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 purpose and output, then limits and disclaimers; every clause carries information. It is a single very long run-on sentence with stacked parentheticals ('(JSON with unescaped slashes and unicode)'), which costs some readability but not content.

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?

For a 3-parameter tool with a full input schema and an output schema, the description supplies everything an agent needs: acceptable input sources, the default for the optional second file, the vendor cap, the no-fetch/no-storage behavior, and the meaning of the returned sha256. Return-value detail is correctly left to the output schema.

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 adds real semantics the schema lacks: the behavior when optional parameter 'b' is omitted (OwnYourAgent's own answers from get_vendor_answers become the second file). It adds nothing for 'lang' beyond the enum already in the schema, and the format-version handling is left to 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?

Specific verb and resource: 'Compares two answer files of the Ownership Check (Eigendomscheck) question by question', followed by the exact output shape (per-ID answers per vendor, proof-URL presence, diff flag, per-vendor counts, sha256). An agent can distinguish this comparison tool from the retrieval sibling get_vendor_answers, which is named as a file source rather than a substitute.

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?

Gives the key conditional: 'Without "b", the own answers of OwnYourAgent (get_vendor_answers) are the second file', plus the operational constraint 'At most 8 vendors in total' and 'pass the files themselves' since the server fetches nothing. It also sets scope boundaries ('compares self-declarations; it does not certify anyone. Not legal advice'), though it does not name a sibling to use instead for other tasks.

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