Trooth

trooth_ask

Read-onlyIdempotent

Answer a question about Trooth itself (what the Trooth Network is, what one company record carries, pricing, how witnessing works) from Trooth's fixed, curated knowledge base. Makes no outside request. A question the knowledge base does not cover returns out_of_scope; for a company's record use trooth_public_trust_profile.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`question`	Yes	A question about Trooth

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.9/5.0

Behavior5/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds valuable context beyond those: 'Makes no outside request,' 'fixed, curated knowledge base,' and the explicit out_of_scope return for uncovered questions. This clarifies the tool's operational boundaries without contradicting annotations.

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?

Three tightly written sentences front-load the core purpose and scope, then add the key behavioral note and sibling routing. Every sentence earns its place with no repetition or 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?

Given the single parameter, rich annotations, and presence of an output schema, the description fully covers what the tool does, when to use it, what it returns for out-of-scope questions, and how it differs from a sibling. Nothing an agent needs to invoke it correctly is missing.

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% and the parameter is a simple required string described as 'A question about Trooth.' The description adds meaning by scoping the question to Trooth's knowledge base and specifying the out_of_scope behavior, which helps the agent craft valid inputs. It stops short of giving example phrasings, but the added context is sufficient.

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 uses a specific verb ('Answer a question about Trooth itself') and identifies the resource (Trooth's fixed, curated knowledge base). It enumerates example topics and explicitly contrasts with trooth_public_trust_profile, so an agent can distinguish it from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly states when to use the tool: for questions about Trooth itself, not about a company's record. It names the alternative trooth_public_trust_profile for company records and explains the out_of_scope return behavior, giving the agent actionable selection criteria.

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.