Skip to main content
Glama

OwnYourAgent

Get the OwnYourAgent trust register

get_trust_facts
Read-onlyIdempotent

Returns the trust register of OwnYourAgent, the same file as https://ownyouragent.com/trust.json: every promise about privacy and security that is true today (no cookies, first-party only, HTTPS, a security contact, closed internal paths, where request data is held, a read-only MCP server), where it is stated, and for each one or more verify steps you can run yourself with plain GET requests (URL plus the expected status, header, text or JSON field). Also what is explicitly not claimed (no certification, no penetration test). Use it when the user asks whether OwnYourAgent can be trusted; run the verify steps before you rely on an entry. 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_trust_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
siteYes
contactYes
entriesYes
relatedYes
versionYes
$commentYes
publisherYes
source_urlYes
not_claimedYes
last_reviewedYes
security_contactYes

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real value beyond them: it discloses that the payload mirrors https://ownyouragent.com/trust.json, that verification is done with plain GET requests against URLs with expected status/header/text/JSON, and that some things are explicitly not claimed (no certification, no penetration test).

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 core statement of what is returned, followed by the usage instruction and the caveat. The parenthetical enumerating every promise is dense but each item earns its place by signalling what an agent will find; the only redundancy is restating the URL/file identity in two ways.

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 zero-argument, read-only lookup with an output schema and full annotations, the description supplies everything an agent needs: what the register contains, where it comes from, how to independently verify entries, and what is deliberately not asserted. Return-value shape is covered by the output schema, so no gap remains.

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?

The tool takes zero parameters and the description closes the loop with 'No arguments.' Baseline for a parameterless tool is 4; nothing further is needed.

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 trust register of OwnYourAgent') and then enumerates the register's contents (no cookies, HTTPS, security contact, closed paths, data residency, read-only MCP server). That level of detail lets an agent distinguish it from siblings like get_approach or get_offers without opening the schema.

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 trigger — 'Use it when the user asks whether OwnYourAgent can be trusted' — plus an ordering instruction to run the verify steps before relying on an entry. It does not name a sibling or a when-not condition, so it falls short of a 5.

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