Trooth

trooth_public_trust_profile

Read-onlyIdempotent

Read one company's published record on the Trooth Network, given its domain or Trooth slug. The identifier is matched exactly (a URL is reduced to its host), never by a similar name. Returns a status (published, listed, private, unclaimed or unavailable) and a provenance label; text the company wrote about itself is labeled as its own words. Read only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`company`	Yes	Company domain (e.g. acme.com) or Trooth slug

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes	Machine-branchable outcome for this lookup.
`subject`	Yes	The company, domain or token this answer is about.
`summary`	Yes	The same answer as the text content, for display.
`evidence`	No	Present on a published profile. What this answer is built from, what it leaves out, and where to get the rest. The summary is a summary: the typed facts with their provenance are in the record at full_record.
`claim_url`	No	Present when the subject has no published record (unclaimed or private).
`provenance`	Yes	Where this answer came from. An honest_absence is missing data, never a judgment about the subject. A read_failed means Trooth could not read its own record at this moment and asserts nothing either way; retry rather than concluding. witnessed_reading: a published profile whose reading Trooth witnessed; the profile is not signed, and the one signed object is the reading's witness statement (see evidence.signed_artifact). connected_system_reads: read from systems the company connected. ledger_token_signatures: the result of checking a Trust Ledger Token's two signatures; the claims inside it stay the company's. witnessed_signed is DEPRECATED since 2026-09-26 and no longer returned; it meant any of the three above.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 26, 2026

addedOutput schema / properties / evidence

Added value: +{
+  "description": "Present on a published profile. What this answer is built from, what it leaves out, and where to get the rest. The summary is a summary: the typed facts with their provenance are in the record at full_record.",
+  "properties": {
+    "counts": {
+      "description": "The reading's counts, from the source named. witness_statement: read, as expected and not read in this reading. result_tally: an older reading's own tally, not a count of checks read.",
+      "properties": {
+        "as_expected": {
+          "type": "integer"
+        },
+        "in_reading": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "not_read": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "read": {
+          "type": "integer"
+        },
+        "source": {
+          "enum": [
+            "witness_statement",
+            "result_tally"
+          ],
+          "type": "string"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "facts_published": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "full_record": {
+      "description": "The canonical record as JSON, contract 2, with every typed fact, its provenance and its date where known.",
+      "type": "string"
+    },
+    "last_witnessed": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "omitted": {
+      "description": "What the summary leaves out. Every item is in full_record.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "profile_signed": {
+      "description": "Always false. The profile is not signed.",
+      "type": "boolean"
+    },
+    "schema": {
+      "type": "string"
+    },
+    "signed_artifact": {
+      "description": "The one signed object behind this answer, or null when the reading carries none. It is served, byte for byte as signed, in the witnessStatement field of full_record.",
+      "properties": {
+        "covers": {
+          "type": "string"
+        },
+        "key_id": {
+          "type": "string"
+        },
+        "read_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "type": {
+          "type": "string"
+        },
+        "verify": {
+          "type": "string"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

changedOutput schema / properties / provenance / description

Previous value: -"Where this answer came from. An honest_absence is missing data, never a judgment about the subject. A read_failed means Trooth could not read its own record at this moment and asserts nothing either way; retry rather than concluding."New value: +"Where this answer came from. An honest_absence is missing data, never a judgment about the subject. A read_failed means Trooth could not read its own record at this moment and asserts nothing either way; retry rather than concluding. witnessed_reading: a published profile whose reading Trooth witnessed; the profile is not signed, and the one signed object is the reading's witness statement (see evidence.signed_artifact). connected_system_reads: read from systems the company connected. ledger_token_signatures: the result of checking a Trust Ledger Token's two signatures; the claims inside it stay the company's. witnessed_signed is DEPRECATED since 2026-09-26 and no longer returned; it meant any of the three above."

changedOutput schema / properties / provenance / enum

Previous value: -[
-  "witnessed_signed",
-  "signed_scan",
-  "live_observation",
-  "honest_absence",
-  "withheld_by_owner",
-  "knowledge_base",
-  "input_error",
-  "self_declared",
-  "read_failed"
-]New value: +[
+  "witnessed_reading",
+  "connected_system_reads",
+  "ledger_token_signatures",
+  "witnessed_signed",
+  "signed_scan",
+  "live_observation",
+  "honest_absence",
+  "withheld_by_owner",
+  "knowledge_base",
+  "input_error",
+  "self_declared",
+  "read_failed"
+]

First observedSep 26, 2026

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, and openWorldHint, so the safety profile is covered. The description adds valuable behavioral details: matching is exact, URLs are reduced to host, never similar names, and the output includes a status list and provenance label. This goes beyond the annotations and helps the agent understand edge-case behavior (e.g., exact match only).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, front-loaded with the primary purpose, followed by matching rules and output summary. Every sentence adds essential information without redundancy. No filler or unnecessary elaboration, making it efficient and well-structured.

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?

For a single-parameter read-only tool with an output schema present, the description sufficiently covers input semantics, matching behavior, and the key output components (status and provenance). It lists all possible statuses and explains how self-authored text is labeled. Minor gaps like error handling or exact provenance format are not critical given the output schema exists and the operation is read-only.

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 schema already describes the 'company' parameter as a domain or slug (100% coverage). The description adds critical nuance: it explains that the identifier is matched exactly, and a URL is reduced to its host. This clarifies how the parameter is interpreted, which is not evident from the schema alone. Thus it enriches the semantic meaning beyond the structural definition.

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?

The description clearly states the specific action: 'Read one company's published record on the Trooth Network' with the input being a domain or slug. It goes beyond the title by specifying exact matching behavior, distinguishing it from sibling tools like trooth_ask or trooth_verify which likely serve different purposes. The verb, resource, and matching constraint are unambiguous.

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?

The description gives clear context for use: when you need to read a company's public trust record, given its domain or slug. It does not explicitly mention when not to use it or name alternatives, but the read-only nature and specific resource are enough for an agent to infer the appropriate situation. No exclusions are provided, but the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Trooth tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.