signal-bureau

get_truth_record

The maintained record for one subject — the ONE file its /exhibit page renders from and GET /api/truth/{slug} serves, so their numbers agree by construction and a value-parity gate fails the build if they stop: what the subject is, the first-party documents we read, the claims and how many separate publishers carried each, our own attention, the prediction-market prices we cite (never a probability of ours), the change log, and what this record cannot see. Every subject on the publication registry carries one. Free — public record, no key, no charge. With no argument you get the flagship record (hormuz today, and it rotates). Three answers, never two: served with the record; not-registered when we read the registry and do not maintain that subject (a measured absence); cannot-measure when the record store could not be read (the record may well exist — we could not look). Two of these subjects also have a full public exhibit page a human can read: hormuz, interest-rates, ai-model-race, us-government-shutdown, israel-iran-conflict, russia-ukraine-war, brazil-election, strait-of-hormuz, us-presidential-2028, us-midterms-2026, gaza-ceasefire, fed-rate-decision, venezuela-crisis, uk-election, us-recession-2026, disaster-event-hurricane, disaster-event-atlantic-hurricane, product-launch-spacex, product-launch-falcon-space-force, product-launch-falcon-spacex, product-launch-space-force-spacex, product-launch-spacex-starlink, election-michigan-republican, election-republican-republicans, regulatory-action-hawaii-high-court, election-republican, election-republican-republican-party, ceasefire-peace-iran, election-michael, legal-ruling-supreme-court, regulatory-action-congress, economic-indicator-inflation, disaster-event-earthquake, funding-round-spacex, bitcoin-price-level, product-launch-xai, election-france, election-serbia, product-launch-anthropic, election-british-columbia-united-kingdom, election-democratic-party, election-germany, funding-round-stripe, election-israel, funding-round-perplexity, product-launch-anthropic-claude-opus, economic-indicator-argentina-inflation, election-mecklenburg-vorpommern, election-swedish, economic-indicator-unemployment, election-parliament, election-parliament-russia, election-quebec, funding-round-kraken. Complementary to get_entity, which returns the broader live entity dossier.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`topic`	No	The name this parameter had under get_truth_object. Still accepted, always will be.
`subject`	No	Which subject, by slug or name — "Interest Rates", "interest_rates" and "interest-rates" all reach the same record. Omit for the flagship.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses free/no-key/no-charge access, the three possible answers (`served`, `not-registered`, `cannot-measure`), the rotating flagship default, and that cited prediction-market prices are never the tool's own probability. It omits rate limits and exact record shape, but covers key behavioral traits.

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

Conciseness2/5

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

The description is bloated with a very long, unnecessary list of exhibit-page subjects. While the core purpose and behavior are front-loaded, the extensive enumerations detract from conciseness and do not support correct tool invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description partially compensates by summarizing record contents and return states, but it does not describe the exact structure of the returned record or mention error/limit behavior. It is adequate for a simple lookup tool but not fully complete.

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. The description adds that 'with no argument you get the flagship record (hormuz today, and it rotates),' which goes beyond the schema's 'Omit for the flagship' and clarifies the default behavior for the subject parameter.

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 states a specific verb and resource: it returns 'the maintained record for one subject' and explicitly contrasts with get_entity, which returns 'the broader live entity dossier.' An agent can distinguish this tool from its siblings based on the purpose alone.

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

Usage Guidelines3/5

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

Usage is implied through 'Complementary to get_entity' and the note that omitting the subject returns the flagship record. However, the description does not explicitly state when to prefer this tool over get_entity or other siblings, nor does it provide exclusions or when-not conditions.

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

All signal-bureau 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.

Resources

Need Help?