Skip to main content
Glama

signal-bureau

by io.github.evolutionlabs-dev

get_truth_object

The complete public truth object for a topic — the SAME record the /exhibit page renders, with every layer kept apart and labeled: primary operational sources (verified-as-of dates stated), attributed reporting, our coverage metric, market expectation with the maintained event arc, our derived judgment, the reporting-consensus ledger, and the state-change history. A layer not yet wired for a subject states its pending status on the layer itself — never rendered to look finished. Free — public exhibit data, no key, no charge. Published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, us-midterms-2026, brazil-election, us-presidential-2028, strait-of-hormuz, venezuela-crisis, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, rate-decision-interest-rates, disaster-event-hurricane, funding-round-perplexity, election-darline-graham-graham, election-minnesota-senate, legal-ruling-supreme-court, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-brazil-senate, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-massachusetts, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-senate, election-france-senate, election-georgia-republican, election-michigan-senate, election-minnesota-republican, election-nebraska-republican, election-oklahoma-republican, election-republican-senate, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, election-republican, product-launch-anthropic, funding-round-stripe, product-launch-xai, product-launch-anthropic-claude-opus, election-germany, election-scott, election-democrat-democrats, election-michael, funding-round-kraken, price-threshold-nvidia, election-israel, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-chen, election-democratic-party, election-democratic-party-swedish, election-florida-republican, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-michigan-republican, election-national-assembly, election-oklahoma, election-ontario, election-parliament, election-parliament-russia, election-peru (default: hormuz). Same payload as GET /api/truth/{topic}; the hormuz record is also addressable as the sb://exhibit/hormuz resource. Complementary to get_entity, which returns the broader live entity dossier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoWhich truth object (default "hormuz" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, us-midterms-2026, brazil-election, us-presidential-2028, strait-of-hormuz, venezuela-crisis, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, rate-decision-interest-rates, disaster-event-hurricane, funding-round-perplexity, election-darline-graham-graham, election-minnesota-senate, legal-ruling-supreme-court, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-brazil-senate, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-massachusetts, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-senate, election-france-senate, election-georgia-republican, election-michigan-senate, election-minnesota-republican, election-nebraska-republican, election-oklahoma-republican, election-republican-senate, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, election-republican, product-launch-anthropic, funding-round-stripe, product-launch-xai, product-launch-anthropic-claude-opus, election-germany, election-scott, election-democrat-democrats, election-michael, funding-round-kraken, price-threshold-nvidia, election-israel, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-chen, election-democratic-party, election-democratic-party-swedish, election-florida-republican, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-michigan-republican, election-national-assembly, election-oklahoma, election-ontario, election-parliament, election-parliament-russia, election-peru)

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and delivers: it discloses free keyless access, the pending-status convention for unwired layers, and the 'never rendered to look finished' anti-fabrication behavior. This is meaningful behavioral context beyond what the schema alone provides.

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

Conciseness3/5

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

The opening sentence front-loads the core definition and the closing get_entity contrast earns its place. However, the enormous published-topic list is duplicated verbatim from the input schema, adding substantial bloat without new 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?

Despite having no output schema, the description spells out the seven payload layers, the pending-status behavior, the default topic, and the no-auth access model. For a single-optional-parameter read tool this is largely complete; only unknown-topic error behavior is left unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents the topic parameter including default and the full published list. The description repeats the ~90-topic list verbatim rather than adding new parameter meaning, keeping it at the baseline 3.

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 ('the complete public truth object for a topic'), enumerates the seven labeled payload layers, and explicitly contrasts itself with get_entity ('which returns the broader live entity dossier'). An agent can distinguish it from its closest sibling without inspecting schemas.

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?

Explicitly names the complementary sibling get_entity and explains the difference, and notes the payload equivalence with GET /api/truth/{topic} for agents familiar with the REST API. It does not route against the many other get_* siblings, but none are close enough in function to require exclusion guidance.

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

All signal-bureau toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool targets a distinct function: ask is async event queries, get_answer retrieves results, get_signals and top_accelerating provide different signal views, get_entity and search_entities cover entity details and search, etc. No two tools have overlapping purposes, and descriptions clearly separate them.

Naming Consistency4/5

The majority of tools follow a 'get_' prefix for retrieval (13 of 21) and other clear verbs like 'ask', 'create_order', 'propose_topic', 'send_feedback'. A few use noun phrases like 'todays_brief' and 'top_accelerating', which breaks the pattern slightly but are still intuitive. Overall consistent and predictable.

Tool Count5/5

21 tools cover the full scope of the server: exploration, querying, ordering, account management, feedback, and data records. Each tool serves a clear purpose without redundancy, and the count feels well-scoped for the domain.

Completeness4/5

The tool surface covers all major workflows: browsing signals, asking questions, getting detailed reports, ordering, providing feedback, and proposing new topics. Minor gaps exist (e.g., no explicit tool to cancel an order or manage watched topics directly), but core operations are present and agents can handle the domain effectively.

Resources