Skip to main content
Glama

OwnYourAgent

Get the own answers of OwnYourAgent on the Ownership Check

get_vendor_answers
Read-onlyIdempotent

Returns how OwnYourAgent answers its own Ownership Check, per ID: yes, partial or unknown, with for each answer the proof (a quote and the URL of the page of ownyouragent.com where it stands literally) and, for partial, the gap. It is a self-declaration, not a certificate: check each quote on its URL before you rely on it. The same file is at https://ownyouragent.com/.well-known/ownership-check-answers.json, the place where any vendor can publish its answers in this format (0.2). Use it to compare another vendor with OwnYourAgent, question by question. No arguments.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
byYes
checkYes
formatYes
strictYes
vendorYes
summaryYes
vendorsYes
$commentYes
createdAtYes
selfDeclaredYes
formatVersionYes
notACertificateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, closed-world behavior, and the description adds material context beyond that: the answer taxonomy (yes/partial/unknown), the proof shape, the self-declaration caveat versus a certificate, and the canonical well-known URL with format version 0.2. This is exactly the extra provenance and trust context an agent needs before quoting an answer.

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 what is returned, then the caution, then the sharing principle. Dense but every sentence carries weight; the one nit is 'per ID' near the start, which reads as leftover phrasing rather than actionable information.

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, yet the description still names the returned fields and values, and it explains the underlying file location and version. Combined with the empty input schema and read-only annotations, an agent has enough to fetch and safely interpret the data; only the sibling relationship to get_ownership_check goes unstated.

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?

Zero parameters, so the baseline is 4; the description correctly closes with 'No arguments,' reinforcing the empty schema. Nothing further is required, though the stray 'per ID' phrasing slightly muddies the no-argument claim.

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?

States a specific verb and resource: returns OwnYourAgent's own answers to its Ownership Check, including proof (quote + URL) and the gap for partial answers. The only blur is 'per ID' – the tool takes no arguments, so 'per ID' is ambiguous about how the item is selected, though the no-arg schema resolves it in practice.

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 an explicit use case ('use it to compare another vendor with OwnYourAgent, question by question') and a handling instruction ('check each quote on its URL before you rely on it'). It does not name a sibling alternative 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