SigB (Signal Bureau): maintained, source-traced record of entities and events in your named domain.
Ask what the tracked record shows about a named entity or unfolding event (geopolitics, markets, tech, health): what changed, what the maintained record currently holds, and which sources corroborate it. NOT for historical facts or general knowledge — grounding is live tracked coverage, and each call does real model work and rides your identified key: self-issue one FREE in a single call (POST /api/keys with {"label":"your agent name"} — instant, no human, no card; the response's key field, shown once, rides back as an x-api-key header) and it carries 25 free asks for the life of the key on its own meter — not per day, and they do not reset; after them each Read meters at the published rate on a billing arrangement you open with create_order (item 'api'), never by default, and a used-up allowance answers with that step, never a dead end — never shared with your cloud or platform neighbors (universal keying, 2026-08-08; an unkeyed call returns the same one-step instruction). ASYNC BY DEFAULT: returns a claim ticket in ~1s ({status:'working', ticketId}); collect the finished answer with get_answer (typically ready in 30-120s, free to collect — the question was metered once at submit). Keep working while the desk works. If the ticket store is briefly unavailable the full answer comes back synchronously instead — handle both shapes. SHARED STATE: the same question asked again while the record's answer is recent returns the SAME stored answer immediately (servedFrom:'maintained-record', same permalink id) — that consistency is the product behaving as documented, and a served-from-record answer is still one Read on your meter (the maintained state IS what was bought); pass fresh:true to re-synthesize. VERIFICATION VERDICT (sourceChecked): true means every load-bearing claim was located in article-level coverage, at least one cited source is independent of Signal Bureau, AND no claim asserts a stronger operational state than the cited evidence supports (risk, disruption, incident and halt are graded, not interchangeable); a hard claim whose only support is a headline, or one stronger than its evidence, is listed in the caution list and caps the verdict and confidence — pass/fail is always disclosed, with what would change the read. For browsing what is moving, prefer get_signals/top_accelerating (cheap, 500/day). Informational only — not advice.
| Name | Required | Description | Default |
|---|---|---|---|
| fresh | No | Force a new synthesis instead of the maintained record's recent answer to the same question (default false — shared state is the default) | |
| question | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does so thoroughly. It discloses authentication/key issuance, free-tier metering and billing behavior, shared-state consistency with servedFrom:'maintained-record', the effect of fresh:true, and the verification verdict logic (sourceChecked, caution list, graded claims). This is far beyond a minimal read/write label.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is information-dense but overly long: it front-loads purpose, then spends many sentences on key issuance, meter details, billing, shared-state behavior, and verification rules. Some asides (e.g., 'universal keying, 2026-08-08') are tangential to using the tool. It is organized but would benefit from tighter structure.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no output schema and no annotations, the definition covers essentially all needed context: valid question scope, result semantics, auth/metering, consistency behavior, verification output, and alternatives. There is no obvious missing piece for an agent to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema explains fresh in detail but leaves question as a bare string. The description compensates by defining what the question should address (named entity or unfolding event in tracked coverage) and what the answer will cover. It doesn't give explicit question examples or length constraints, so it's not a perfect 5, but it adds clear semantic guidance.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb and resource: 'Ask what the tracked record shows about a named entity or unfolding event.' It also names the output dimensions (what changed, current holdings, corroborating sources) and explicitly excludes historical facts/general knowledge, which differentiates it from generic Q&A and sibling tools like get_entity or get_record.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives an explicit 'NOT for' boundary and directs an alternative for a different use case: 'For browsing what is moving, prefer get_signals/top_accelerating (cheap, 500/day).' It also specifies when to pass fresh:true ('re-synthesize') vs relying on shared state, giving clear selection guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Assemble a basket and get exact prices plus Stripe checkout links. Checkout runs on Stripe's hosted page, completed by whoever holds the payment credentials. Pass dryRun:true to REHEARSE: same validation, same price math, clearly labeled, no order recorded, no links issued, nothing billed — integration-test the full flow risk-free. Item ids — plans: 'analyst', 'power', 'pilot', 'desk-private', and 'api' (the Metered API account: your identified key — self-issue one FREE at POST /api/keys, no human in the loop — with billing activated by the desk on this order, usage billed monthly at tariff rates, nothing preset — get_quote prices your exact basket first, get_account shows the live statement); unit: 'watch' (reads of the watched question included). Reads are metered per use at the flat tariff rate, never sold as prepaid packs. Live prices come from /api/tariff; this description states none. Watch topics are SELF-SERVE end to end: pass topics and every one comes back with a checkout link at the published Watch rate — including a topic nobody watches yet, whose price the desk mints on demand with no human in the loop (that one needs your identified key, free and self-issued in one call at POST /api/keys, and arrives in minutes; poll get_order or the statusUrl on the line). The api line still records intent and the desk activates the account. Every line states its own state and what to do next.
| Name | Required | Description | Default |
|---|---|---|---|
| No | Contact email to attach to the order intent (optional) | ||
| items | Yes | Array of {id, quantity?} — catalog ids above; quantity applies to unit items only | |
| dryRun | No | true → rehearse: validate + price the basket, record nothing, issue no links, bill nothing | |
| topics | No | Optional: the quoted topic names (or 1-based topic numbers as strings) this order's Watch lines cover — carried verbatim onto the recorded intent so scoped concerns survive the quote→order handoff. Max 12, each ≤200 chars. | |
| quoteId | No | Optional: the quoteId from get_quote — recorded on the order intent so the desk provisions against that exact quote. | |
| idempotencyKey | No | Optional client key (≤128 chars): makes the orderId deterministic and a retried call return the original intent instead of recording a second one — safe machine retries |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description fully owns behavioral disclosure. It covers external Stripe-hosted checkout, dry-run side effects (no order, no links, no billing), billing mechanics for the API plan, self-served watch topics, and the fact that topics can be minted on demand. This goes far beyond a simple 'create an order' statement.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is information-dense but also a long single paragraph with run-on structures and digressions like tariff note and key issuance details. It is not well structured or easily scannable; with more forbidding, the same depth could be delivered more concisely.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers main operational behavior, catalog specifics, dryRun, watcher topics, and what type. However, with no output schema, the exact response shape—orderId, checkout links, line-level statuses—is only hinted at via 'every line states its own state' and 'statusUrl on the line'. More explicit return-value clarification would make it fully outward factor.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers 100% of parameters, but the description adds important catalog semantics not present in the schema: plan identifiers, the watch/read unit, the Metered API key flow, and the fact that reads are never prepaid. That added meaning helps the agent determine valid item ids and shape the items array correctly.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly frames create_order as the tool for assembling a basket into an order with exact prices and Stripe checkout links, and differentiates it from get_quote by noting quote flow and from get_order by mentioning polling order status. The wording 'no order recorded' for dryRun confirms the normal path records an order, so the intended resource is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives concrete guidance on when to use dryRun for rehearsal versus a real transaction, and points to get_quote for pre-pricing and get_order/statusUrl for post-order status. It does not explicitly state 'use get_quote instead when you only need pricing,' but the relationship is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Your meter-account statement, live: month-to-date metered Reads counted at the published tariff, your watched topics with billing/billing status and their acceptance evidence, and your daily cap. Requires your identified key on the request (x-api-key header, or authorization: Bearer sb_live_...). Without a key this tool explains how to get one — every read surface stays available in the free anonymous lanes either way. Recognition is opt-in via credential: no key, no tracking.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does well: it discloses authentication methods (x-api-key or Bearer sb_live_...), behavior without a key (explains how to get one), privacy stance ('no key, no tracking'), and what data is returned. It implies read-only via 'read surface' and 'statement' but could be more explicit about not modifying anything; it does not mention error handling or rate limits, so not a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and front-loaded: it starts with the main output ('Your meter-account statement, live'), then details the contents, followed by authentication requirements and fallback behavior. Each sentence adds essential information without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no parameters and no output schema, the description is quite complete: it enumerates the return contents, explains authentication, and covers the no-key case. It lacks explicit return format (e.g., JSON vs text) or possible failure responses, but given the simplicity, it is sufficiently complete for an agent to select and invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters and the schema is empty (100% coverage by default). The description adds context about authentication headers (x-api-key, Bearer) which is not in the schema, aiding the agent in constructing the request. Since there are no parameters, the baseline is 4, and the description adds no unnecessary parameter info.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as providing a meter-account statement with specific contents: month-to-date metered Reads, tariff, watched topics with billing status, acceptance evidence, and daily cap. It distinguishes from sibling get_* tools by focusing on account/billing-specific data, using the phrase 'your meter-account statement' which is distinct from other tools like get_entity or get_watch_feed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides context on when to use the tool: it requires an identified key, and without a key it explains how to get one. It also mentions that read surfaces remain available in free anonymous lanes, giving an alternative access path. However, it does not explicitly compare to sibling tools or state exclusions for specific scenarios, 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.
Collect an async answer by ticketId (from ask). Free and unmetered — the work was paid for once at submit. status:'working' → poll again after pollAfter seconds; 'done' → the complete answer rides in this response; 'failed' or 'lost' → the reason, stated plainly, and asking again is the remedy.
| Name | Required | Description | Default |
|---|---|---|---|
| ticketId | Yes | The uuid the ask tool returned |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden and succeeds. It discloses the cost model ('free and unmetered'), the asynchronous status lifecycle, the fact that 'done' includes the complete answer, and the action needed for failures. This is far beyond minimal disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded: the first phrase states exactly what the tool does, and every subsequent clause earns its place by explaining polling behavior, cost, and terminal states. No filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter tool with no output schema, the description fully explains the integration point (from ask), the response states, the polling interval, the cost implication, and the failure remedy. The agent has everything needed to invoke and interpret the result correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% because the only parameter, ticketId, is already described as 'The uuid the ask tool returned'. The description's reference to 'ticketId (from ask)' adds no new semantic detail beyond what the schema provides, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Collect') with a clear resource ('async answer by ticketId'), explicitly ties to the 'ask' tool, and differentiates itself from sibling get_* tools by focusing on asynchronous result retrieval. The status-based outcome states make the purpose unmistakable.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides explicit conditional guidance: poll after pollAfter seconds when status is 'working', and treat the response as final when status is 'done'. For 'failed' or 'lost', it states the remedy ('asking again'), establishing when to use this tool versus re-submitting via ask.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Deprecated: this tool is winding down — for evaluating or reading the maintained record, use get_truth_object, get_entity/search_entities, and todays_brief instead. Still served here: the grading dataset for the market sensor we cite, and only that — the prediction-market price (crowd) and the naive null it is scored against (base_rate), against how reality resolved (Brier score, log loss, skill vs base rate, 95% CIs), each price captured while its market was OPEN and graded as it matured, so the grade cannot be back-filled. No forecaster of ours is published, here or in the full dataset: we sell a maintained, source-traced record and cite market prices as one graded sensor, not a forecast of ours. Full dataset with reliability bins: GET /api/calibration-data.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It adds significant context: deprecated status, what data is served (grading dataset for market sensor), that it is scored while open and graded as matured (cannot be back-filled), and that no forecaster is published. However, it does not explain behavior like response format or potential errors, but for a deprecated tool, the disclosure is fairly thorough.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a long single block of text, somewhat dense and not front-loaded. It is informative but could be broken into clearer sections (e.g., deprecation notice, what it returns, what it does not return). It earns its place but could be more structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool is simple (no parameters, no output schema), the description covers the key aspects: deprecation, alternatives, what data is included, and what is not included. It also points to a full dataset endpoint. This is complete enough for the agent to decide if and how to use it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters, and schema coverage is 100% (trivially, since there are no parameters). The description adds context about what data is returned (fields like crowd, base_rate, Brier score, log loss, etc.), which is useful for the agent to understand the output even without an output schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states it is deprecated and what it serves: the grading dataset for the market sensor (crowd and base_rate) with performance metrics. It clearly identifies the resource and distinguishes it from siblings by explicitly naming alternatives (get_truth_object, get_entity/search_entities, todays_brief).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states the tool is deprecated and tells users to use specific alternatives for maintained data. It also clarifies what is not included (no forecaster published) and directs to a full dataset endpoint. This provides clear when-to-use and when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
A newsletter DESK's machine feed at one predictable, slug-addressable location: up to 14 days of the desk's observed items (title, url, source), newest-first, from the same panel the human edition reads. Unlike watch topics, the desk roster is PUBLIC PRODUCT — the desks are: cognitive-investor, tax-nexus, crc-kras, crc-digest, space-economy, paradise-valley, lyt-intel, aztc-aasd, newspace-asu, lq-listening, jedi-knowledge, ud-articles, ecomm-news — so an unknown-desk reply lists them freely. Delivery is keyed (your self-issued key, x-api-key): identified delivery is the standard shape for standing feeds. Desks are priced as labeled topic bundles at the published Watch rate — see DESK_BUNDLES on /api/tariff and get_quote for your exact basket. Each feed's payload declares its own coverage state.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | How many recent days to return (1-14, default 14) | |
| desk | Yes | The desk slug (e.g. 'space-economy') |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description discloses ordering ('newest-first'), time window ('up to 14 days'), item fields, keyed authentication ('x-api-key'), behavior for unknown desks, and that payload declares coverage state. It does not explicitly state read-only semantics, but the feed nature strongly implies it.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is moderately long but each sentence contributes unique information: purpose, roster, delivery, pricing, and coverage state. It is front-loaded with the core function, though the desk list and pricing details add extra length.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations and output schema, the description covers retrieval scope, authentication, differentiation from watch topics, and pricing. It does not detail error cases or exact response envelope, but the mention of 'payload declares its own coverage state' mitigates some uncertainty.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already covers both parameters with descriptions and examples. The description adds the full list of valid desk slugs and clarifies the days parameter as a lookback window, enriching the parameter meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns a desk's machine feed: 'up to 14 days of the desk's observed items (title, url, source), newest-first'. It also distinguishes itself from sibling tools by explicitly contrasting with 'watch topics' and naming the public desk roster.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides context for when to use: 'identified delivery is the standard shape for standing feeds' and contrasts with watch topics. It also directs to get_quote for pricing, but does not explicitly state 'use this instead of X' except through the watch topic differentiation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Full dossier for one entity: signal count, verticals it's spreading across, and why it's surfacing.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the burden. It discloses the kind of return data (signal count, verticals, why surfacing) but does not state read-only behavior, error handling, or side effects. Adequate for a simple getter but incomplete on safety context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence that efficiently communicates the tool's purpose and key output components with no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter getter, the description covers what it does and what it returns. Given the large sibling set, adding a note about when not to use it would aid completeness, but the current description is nearly sufficient for selection.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema only has a bare 'name' string with no description (0% coverage). The description compensates by indicating that the parameter identifies a single entity, adding meaning beyond the schema field.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it returns a 'full dossier for one entity' with specific contents: signal count, verticals, and why it's surfacing. This distinguishes it from sibling tools like get_signals or get_record by emphasizing a comprehensive, single-entity view.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use when a deep dive on one entity is needed, but it does not explicitly state when to use this tool versus alternatives like search_entities or get_signals. No exclusions or alternative tool names are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tracked world events (situations, races, negotiations) the engine follows as named arcs — each with its entities, related market-question count, cross-domain mention volume, and first/last-seen dates. Optional query filters by name or entity.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many (default 20, max 50) | |
| query | No | Filter by event name or entity (optional) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden; it details the event structure (entities, market-question count, across-domain mention volume, dates) and optional filters. However, it does not explicitly disclose read-only behavior, return format, or ordering/pagination details beyond the schema's limit parameter.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, directly states the core content and the available filter, with no redundant wording. It front-loads the purpose and avoids filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, so the description compensates by enumerating what each event includes. It covers the main use case and filter capability, though it could be clearer about the response being a list and any default ordering.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already provides 100% coverage for both parameters (limit and query), so the baseline is 3. The description adds that 'query' filters by name or entity, which mirrors the schema and provides no additional syntax or format details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as returning tracked world events, describing them as named arcs with entities and metrics, which distinguishes it from sibling tools like get_entity or get_record. The verb is implied via the tool name 'get', and the scope is well-defined.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies it should be used to retrieve world events, but does not explicitly contrast it with any of the many sibling get_* tools. It gives context about events being engine-tracked arcs, so an agent can infer when to use it, but no explicit when/where-not guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
The state of a report you filed via send_feedback, by its feedbackId: filed, working, or resolved — with its work-order reference. A report filed in the last few hours may still read 'filed'; the response states where it is.
| Name | Required | Description | Default |
|---|---|---|---|
| feedbackId | Yes | The feedbackId returned by send_feedback |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the possible status values, the inclusion of a work-order reference, and the fact that recent reports may still show 'filed'. This provides meaningful behavioral context beyond just saying 'get status'.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the core function, and contains no fluff. It efficiently conveys the status values and a relevant caveat.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given a single required parameter and no output schema, the description provides the status set, the work-order reference, and a timing nuance. This is sufficient for an AI agent to select and invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already describes feedbackId as the value returned by send_feedback (100% coverage). The description adds no new format or syntax details, so it does not improve on the schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns the state of a report filed via send_feedback, listing the possible statuses (filed, working, resolved) and mentioning the work-order reference. It distinguishes itself from sibling get_* tools by focusing specifically on feedback status.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when a feedbackId from send_feedback is available, and provides a temporal caveat about recent reports potentially still reading 'filed'. It does not explicitly name alternatives, but the context is clear given the sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Re-read an order intent created by create_order — the recorded basket and its honest status. Payment truth for checkout purchases lives with Stripe (the payer's receipt is authoritative); metered work is receipted on your meter account and readable via get_account.
| Name | Required | Description | Default |
|---|---|---|---|
| order_id | Yes | The UUID returned by create_order |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses that the operation is a re-read, specifies the output (basket and honest status), and adds important context about payment truth residing with Stripe. It does not mention side effects, but none are expected for a read operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no wasted words. The first sentence states the core purpose, and the second provides necessary caveats. Information is front-loaded and easy to scan.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-by-id tool with one parameter and no output schema, the description adequately explains what the tool returns ('recorded basket and its honest status') and provides essential caveats. No additional information seems necessary for an agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the parameter is documented as 'The UUID returned by create_order'. The description adds no significant new meaning beyond the schema, merely echoing 'created by create_order'. Baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 're-read' and identifies the resource as 'an order intent created by create_order', which clearly indicates its function. It also distinguishes itself from siblings by stating that payment truth and metered work receipts reside elsewhere.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when this tool is appropriate (reading an order intent) and explicitly notes alternative sources for payment truth (Stripe) and metered work (get_account). However, it does not explicitly state 'use this when you need the basket', relying on inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Feed in your requirements — free-form concerns, questions, whole areas of interest — and get back an enumerated quote: your requirements intelligently grouped and disambiguated into well-formed watched topics, each priced flat from the published tariff ($20/topic/month at the opening rate). The count is disclosed in BOTH directions: overlaps are merged, broad requirements are split into the separate daily reports they actually need, and billing.expansion states the requirement-to-topic ratio outright so a split is as visible as a merge. Large baskets are resolved in batches, so a requirement the desk cannot place does not sink the rest: you get a quote for everything it could place, partial: true, and unresolvedRequirements naming what it could not and why — never a topic invented to cover a gap. A quote is not a charge, needs no contact details, and holds for 30 days. Real model work: ~10 quotes/day per network address (shared egress shares the allowance).
| Name | Required | Description | Default |
|---|---|---|---|
| requirements | Yes | What you want watched, in your own words — one blob of text or bullet points; the desk does the grouping |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses numerous behaviors: merging/splitting logic, partial quotes with unresolvedRequirements, rate limits, no contact details, and holding period. This is especially valuable given no annotations are provided.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is dense but well-structured, front-loading the core purpose and then adding necessary detail. It's longer than average but every sentence adds critical information for a complex tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description explains key return fields (billing.expansion, partial, unresolvedRequirements) and the behavior under partial resolution. It also covers rate limits and validity period, making it highly complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already describes the 'requirements' param well, and the description reinforces it with examples and explains how the requirements are processed (grouped, disambiguated). It adds value beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the function: feed in requirements and receive an enumerated quote with grouped watched topics and pricing. The verb 'get back' and resource 'quote' are explicit, and the detailed account of grouping/pricing distinguishes it from siblings like ask or create_order.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explains that this is for requirements that need to be priced and grouped into watched topics, and notes that a quote is not a charge and holds for 30 days. It doesn't explicitly mention alternatives or when not to use, 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.
Deprecated: this tool is winding down — for evaluating or reading the maintained record, use get_truth_object, get_entity/search_entities, and todays_brief instead. Still served here: the correction record — the flagged-vs-control repricing regression at population level (estimate, 95% CI, cohort sizes, window, as-of), plus the dated retirement object for the case-study track record we withdrew in 2026 when re-measurement put it under our own publication bar. Appended, never edited — including about ourselves. Same object: GET /api/record-data.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses that the data is 'Appended, never edited' and that the tool is being deprecated, which are important behavioral traits. It also implies a read-only operation via 'GET /api/record-data', though it doesn't cover auth or rate limits. This is sufficient for a read-only tool with no side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is moderately long but front-loads the deprecation and alternatives immediately. Each sentence adds value: deprecation notice, what is still served, integrity guarantee, and API reference. It could be slightly trimmed but is well-structured and not wasteful.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, so the description must convey what the tool returns. It does so by detailing the correction record (with estimate, CI, cohort sizes, etc.) and the retirement object. It also mentions the append-only nature. This is complete for a no-param read tool, though it omits example response format.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and the schema has 100% coverage (empty object). Per the rubric, a baseline of 4 applies since no parameters exist. The description doesn't need to explain parameters, and it doesn't, so the baseline holds.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool is deprecated and explicitly defines its remaining purpose: serving the correction record and retirement object. It names specific content (repricing regression with statistical details) and points to alternatives, making it distinct from sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says 'Deprecated: this tool is winding down' and lists alternative tools (get_truth_object, get_entity/search_entities, todays_brief) for maintained access. It also conditions when to still use this tool ('Still served here...'), giving clear usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
START HERE for browsing — the cheap read (500/day, no model work). The full machine-readable signal feed (same payload as GET /api/signals): every entity currently flagged by the attention engine, with trajectory, domains, desk membership, and an explicit evidenceStatus (receipted rows carry source-attributed evidence URLs; unreceipted rows are labeled leads). Measured property: Measured association: flagged markets repriced materially at 1.52x the rate of matched unflagged controls (95% CI 1.22-1.73, shock-days excluded, controls reweighted to the flagged cohort; n=2039 flagged vs 84517 controls, window 2026-03-29 to 2026-09-05, as of 2026-09-05). An attention-leads-movement association — never a directional claim.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many signals (default all flagged) | |
| direction | No | Filter by trajectory: rising|fading|steady|new |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden and does substantial work: it discloses the quota (500/day), read-only nature ('cheap read'), payload contents, the distinction between receipted and unreceipted evidence rows, and an explicit caveat that the association is never directional. Only minor invocation details like sorting or pagination behavior are absent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The opening is well front-loaded and useful, but the long 'Measured property: Measured association...' statistical block, including the duplicative 'Measured' label, is tangential to invoking the tool and bloats the description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with no output schema and no annotations, the description is adequately complete: it states what the feed contains, how evidenceStatus behaves, the associated quota, and even hedges the interpretation of the signal. It does not give explicit return formatting, but 'machine-readable feed' plus the field list covers the essential agent needs.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema coverage is 100%, so the schema already documents both parameters. The description reinforces the 'limit' default indirectly and mentions trajectory as an output field, but adds no new syntax or value semantics beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description opens with 'START HERE for browsing' and identifies the resource as the full machine-readable signal feed of every entity currently flagged by the attention engine. It lists payload fields (trajectory, domains, desk membership, evidenceStatus), making the purpose concrete. However, it does not explicitly name sibling tools to contrast with, so differentiation relies mostly on the 'full feed' and 'cheap read' phrasing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'START HERE for browsing' and 'the cheap read (500/day, no model work)' provide clear positive usage context and set expectations for when to use this tool. It does not state exclusions or point to alternatives such as get_desk_feed or top_accelerating, so it falls short of the most explicit route-it guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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, russia-ukraine-war, israel-iran-conflict, gaza-ceasefire, us-midterms-2026, us-presidential-2028, brazil-election, us-government-shutdown, venezuela-crisis, strait-of-hormuz, 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, disaster-event-atlantic-hurricane, rate-decision-interest-rates-irs, funding-round-perplexity, economic-indicator-unemployment, election-michael, election-republican-republicans, election-alabama-republican, election-arkansas-republican, election-florida-republican, election-georgia-republican, election-kansas-republican, election-michigan-republican, funding-round-spacex, regulatory-action-congress, election-republican, election-scott, ceasefire-peace-iran, election-alaska, election-alaska-senate, election-darline-graham-graham, election-darline-graham-republican, election-democratic-party-massachusetts, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, product-launch-xai, funding-round-stripe, election-germany, product-launch-anthropic-claude-opus, election-israel, election-democrat-democrats, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-brazil-senate, election-chen, election-democratic-party, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-russia, election-democratic-party-senate, election-democratic-party-swedish, election-france-senate, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-michigan-senate (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.
| Name | Required | Description | Default |
|---|---|---|---|
| topic | No | Which truth object (default "hormuz" — published: hormuz, interest-rates, ai-model-race, russia-ukraine-war, israel-iran-conflict, gaza-ceasefire, us-midterms-2026, us-presidential-2028, brazil-election, us-government-shutdown, venezuela-crisis, strait-of-hormuz, 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, disaster-event-atlantic-hurricane, rate-decision-interest-rates-irs, funding-round-perplexity, economic-indicator-unemployment, election-michael, election-republican-republicans, election-alabama-republican, election-arkansas-republican, election-florida-republican, election-georgia-republican, election-kansas-republican, election-michigan-republican, funding-round-spacex, regulatory-action-congress, election-republican, election-scott, ceasefire-peace-iran, election-alaska, election-alaska-senate, election-darline-graham-graham, election-darline-graham-republican, election-democratic-party-massachusetts, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, product-launch-xai, funding-round-stripe, election-germany, product-launch-anthropic-claude-opus, election-israel, election-democrat-democrats, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-brazil-senate, election-chen, election-democratic-party, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-russia, election-democratic-party-senate, election-democratic-party-swedish, election-france-senate, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-michigan-senate) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the data is public, requires no key, has no charge, names the equivalent REST endpoint and sb:// resource, and explicitly states that unfinished layers report pending status rather than appearing complete. It does not discuss rate limits or error behavior, but the key operational traits are covered.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Core information is front-loaded and substantial, but the description is bloated by a very long topic list that is repeated verbatim in the input schema. The layered-structure explanation is useful, but the redundant enum list makes the description needlessly long.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter, public, read-only data tool with no output schema, the description covers return structure via the labeled layers, accepted topic values, the default, auth/cost, an equivalent endpoint, and the relationship to get_entity. It does not spell out response serialization or failure modes, but nothing essential for a correct call is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter, topic, is fully described in the input schema with a default and an explicit list of valid values, so the baseline score is 3. The description adds only that these are published subjects and restates the default, which does not change the semantic meaning of the parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The opening phrase 'The complete public truth object for a topic' names a concrete resource, and referencing the /exhibit page anchors exactly what the payload is. It also differentiates itself from get_entity by noting that get_entity returns the broader live entity dossier, so sibling confusion is avoided.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context: this is the free, public, layered truth record for a topic, with a default of hormuz and a list of published topics. It names the closest sibling, get_entity, and draws a clear boundary between a truth object and a broader entity dossier, though it does not give explicit when-not-to-use guidance for every sibling.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
The structured daily delivery for a machine-watched topic: up to 14 days of observed items (title, url, source, date) newest-first, plus the topic's live coverage-acceptance report, which grades the coverage and shows the evidence (it does not gate billing — billing starts when the Watch starts, and the month you are in is refundable in full, any time you ask, for any reason). Delivery is pull: poll daily or on demand. Topics not yet watched: get_quote prices them.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | How many recent days to return (1-14, default 14) | |
| topic | Yes | The watched topic name (as quoted/ordered) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does well. It discloses delivery mode (pull), output structure (newest-first items, grading report), and billing behavior (does not gate billing, month refundable). This goes beyond basic read-only/write categorization and provides useful operational context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single long paragraph with the billing policy embedded, which is tangential to tool invocation. While dense with useful information, it lacks front-loading and includes extra commercial details that could be trimmed without losing operational clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description adequately covers return contents (observed items with fields, coverage report), ordering, delivery mode, and billing implications. With no output schema, it effectively explains what the tool returns. Minor gaps like error handling or missing-topic behavior keep it from a 5.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for both parameters, so baseline is 3. The description adds minor context like 'up to 14 days' matching the schema and 'newest-first' which describes output ordering, not parameter meaning. It doesn't meaningfully enrich parameter semantics beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: it delivers a structured daily feed for a machine-watched topic, including up to 14 days of observed items and a coverage-acceptance report. This specific verb+resource (get/feed) distinguishes it from siblings like get_quote and get_desk_feed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says when NOT to use this tool: 'Topics not yet watched: get_quote prices them.' This provides a clear alternative for unwatched topics and implies this tool is for already-watched topics. Also notes delivery is pull (poll daily or on demand), giving clear usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
START HERE on first contact — the front door. Who Signal Bureau is, what's free (most things), what's paid (work: Watches and Reads), the live tariff with real prices, how to propose new coverage, and how buying works. No side effects, costs nothing.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states 'No side effects, costs nothing,' which clearly indicates that the tool is safe and free to use. This is significant behavioral information for an agent. It doesn't describe the return format, but no output schema exists, and the description sufficiently covers the non-destructive, no-cost nature.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and front-loaded, beginning with the key directive 'START HERE' and the metaphor 'the front door.' It efficiently lists the covered topics in a single follow-up sentence and concludes with the safety statement. Every sentence adds value, with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity (zero parameters, no annotations, no output schema), the description is complete. It explains what the tool does, what information it delivers, and its safety profile. The description fully equips an agent to understand when and why to invoke it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the schema coverage is trivially complete. Per the rubric, a zero-parameter tool receives a baseline score of 4. The description adds no parameter-specific information, but none is needed since there are no parameters to explain.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies this tool as the starting point for first contact ('START HERE', 'the front door'), which distinguishes it from sibling tools. It enumerates the specific information it provides (who Signal Bureau is, free/paid content, tariffs, proposing coverage, buying), making its purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use the tool: 'START HERE on first contact.' This provides clear context for its role as the entry point. While it doesn't name alternative tools or when not to use it, the 'START HERE' guidance implies that other tools are used after orientation, so the usage context is well defined.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Propose NET-NEW coverage — a topic, entity, or standing question we don't track yet. Files into the coverage-request queue humans review; accepted topics enter the provisional coverage lane and start appearing in the signal feed. Needs your human principal's contact email for follow-up. Free.
| Name | Required | Description | Default |
|---|---|---|---|
| why | No | Why this coverage matters (optional — helps the review) | |
| Yes | Your human principal's contact email, used only to follow up on this request | ||
| topic | Yes | What to cover — a topic, entity, or standing question | |
| requester | No | Name to file the request under (optional) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It transparently describes the workflow: files into a queue, humans review, accepted topics enter provisional lane and appear in signal feed. It also mentions 'Free' and the email purpose. Missing are details on rejection behavior, duplicates, or rate limits, but it covers the core process well.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, tightly worded, and front-loaded with the core purpose. Every clause adds value: the net-new scope, the queue outcome, the provisioning lane, the email requirement, and the cost. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity (4 params, no output schema, no annotations), the description sufficiently explains the request lifecycle, including human review and acceptance outcomes. It is missing some edge-case behavior (e.g., duplicate handling, rejection response), but overall an agent can select and invoke this tool with confidence.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and each parameter has a clear description. The tool description adds slight semantic nuance (e.g., 'topic, entity, or standing question' for the 'topic' field) and explains why email is needed, but most meaning is already captured in the schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with a specific verb 'Propose' and a precise resource: 'NET-NEW coverage — a topic, entity, or standing question we don't track yet.' It distinguishes from siblings by emphasizing 'net-new' and the queue/lane workflow, making its unique role obvious.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context on when to use the tool: when proposing something not yet tracked ('we don't track yet'). It also states a prerequisite ('Needs your human principal's contact email') and a cost signal ('Free'). However, it does not explicitly name alternatives or exclusion cases, though the 'net-new' condition implicitly excludes existing coverage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Find tracked entities/topics by name or vertical (e.g. 'iran', 'semiconductors').
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the core action without revealing whether the operation is read-only, what it returns (e.g., list or single entity), or any constraints like case sensitivity or partial matching. This lack of transparency could lead to incorrect assumptions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that front-loads the action ('Find') and immediately specifies the resource and method, followed by examples. Every word earns its place; there is no redundancy or unnecessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one parameter and no output schema, the description covers the basic purpose and query format. However, it does not describe the return value (e.g., list of entities, matched fields) or any behavioral edge cases, leaving some uncertainty for the agent about what to expect from the response.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema only defines a 'query' string with no description, giving 0% schema coverage. The description compensates by explaining that the query can be a name or vertical and provides concrete examples ('iran', 'semiconductors'), adding meaningful semantic context beyond the bare schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function with a specific verb ('Find'), a resource ('tracked entities/topics'), and a method ('by name or vertical'), complete with examples. It effectively distinguishes itself from sibling tools like get_entity by emphasizing a search across entities/topics rather than retrieval of a specific one.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for search scenarios (e.g., finding entities by name or vertical) but does not explicitly state when to use it over alternatives like get_entity or propose_topic. There is no exclusionary guidance, so the agent must infer the appropriate context from the action keyword 'search'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
File structured feedback with the desk: a bug, an improvement, a complaint, praise, or a question about the service itself. Free, no contact details required; limits stated up front: 5/minute, 20/day per network address (shared egress shares the allowance). A complaint that names a real defect becomes our work order — house policy — and get_feedback_status lets you watch the state move by feedbackId. Include ref (a quoteId/ticketId/orderId from your own records) to tie the report to a specific interaction. The response says honestly whether the report was durably recorded.
| Name | Required | Description | Default |
|---|---|---|---|
| ref | No | A quoteId, ticketId, or orderId to tie this to (optional) | |
| kind | Yes | bug | improvement | complaint | praise | question | |
| about | No | Which tool/endpoint/page this concerns (optional) | |
| detail | No | The full story — reproduction steps, expected vs observed (optional) | |
| summary | Yes | One sentence: what happened or what you want |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full transparency burden and excels. It discloses rate limits (5/minute, 20/day per network address), the work-order policy for complaints naming real defects, and the response's honesty about durable recording. These are substantive behavioral details beyond the typical mutation description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is five dense sentences, each adding distinct information: purpose, constraints, behavioral consequence, ref usage, and response guarantee. It is compact, non-redundant, and front-loaded with the core action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given five parameters, no output schema, and no annotations, the description covers purpose, rate limits, side effects, parameter context, and response behavior. The 'honestly' clause partially addresses failure/durability, making the tool's behavior remarkably well-specified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 a small clarification for ref ('from your own records') and re-lists the kind values, but these do not meaningfully exceed the schema's existing descriptions for any parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with 'File structured feedback with the desk', a specific verb+resource that clearly states the tool's purpose. It enumerates the accepted kinds (bug, improvement, complaint, praise, question) and distinguishes this tool from the sibling get_feedback_status by framing it as the follow-up status tracker.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear when-to-use context: it is for filing structured feedback, with constraints (free, no contact details, rate limits) and ref usage guidance. It explicitly names get_feedback_status for tracking, but it does not address potential overlap with siblings like ask, leaving minor ambiguity for service-related questions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Today's morning brief — the daily synthesized narrative of what moved across the information environment and what to watch, from the engine's cross-domain analysis. Same content as the public /today page.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must disclose behavioral traits itself. It explains the content but does not explicitly confirm read-only status, return format, or any special considerations like rate limits or authentication. The reference to the public /today page suggests public accessibility, which is helpful.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that front-loads the tool's identity and provides immediate context. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter read-only tool with no output schema, the description adequately covers what the tool does and what content it returns. The mention of the public /today page provides a reference point for format. It could be improved by explicitly stating the output format or update frequency.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema is empty with zero parameters, so there is nothing to describe. The description appropriately focuses on the tool's purpose rather than parameter semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as providing a daily synthesized narrative, with specific details about cross-domain analysis and 'what to watch'. It distinguishes itself from sibling feeds by referencing the public /today page. However, it lacks an explicit action verb like 'retrieve' or 'get'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this is the go-to tool for a daily overview, but it does not explicitly state when to use it over alternatives such as get_desk_feed or get_watch_feed. No exclusions or alternative tool mentions are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
The entities/topics accelerating most across the information environment right now, ranked by cross-domain attention.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many (default 10, max 50) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It explains what is returned, but does not disclose behavioral traits such as data freshness, filtering behavior, potential rate limits, or whether results are dynamic. The phrase 'right now' implies real-time but lacks specifics.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that directly conveys the tool's core purpose. There is no redundant or extraneous information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description gives a clear high-level purpose but is somewhat incomplete given no output schema. It does not specify what fields are returned (e.g., names, scores, timestamps), which could be useful for an agent. For a simple list tool, it is adequate but has room for improvement.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema fully describes the only parameter 'limit' with a clear meaning and default. The description adds no additional parameter context, but the schema coverage is 100%, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns entities/topics ranked by acceleration and cross-domain attention. It is specific about the resource and ranking, though it lacks an explicit verb like 'list' or 'get', which slightly reduces clarity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. The sibling tools include other list/search tools, but the description does not mention any conditions or exclusions, leaving the agent to infer usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
get_truth_object1 field changedInput schema / properties / topic / descriptionPrevious value: -"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, us-midterms-2026, us-presidential-2028, brazil-election, us-government-shutdown, venezuela-crisis, strait-of-hormuz, 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, disaster-event-atlantic-hurricane, rate-decision-interest-rates-irs, funding-round-perplexity, election-michael, election-republican-republicans, election-alabama-republican, election-arkansas-republican, election-florida-republican, election-georgia-republican, election-kansas-republican, election-michigan-republican, funding-round-spacex, regulatory-action-congress, election-republican, election-scott, ceasefire-peace-iran, election-alaska, election-alaska-senate, election-darline-graham-graham, election-darline-graham-republican, election-democratic-party-massachusetts, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, product-launch-xai, funding-round-stripe, election-germany, product-launch-anthropic-claude-opus, election-israel, economic-indicator-unemployment, election-democrat-democrats, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-brazil-senate, election-chen, election-democratic-party, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-russia, election-democratic-party-senate, election-democratic-party-swedish, election-france-senate, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-michigan-senate)"New value: +"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, russia-ukraine-war, israel-iran-conflict, gaza-ceasefire, us-midterms-2026, us-presidential-2028, brazil-election, us-government-shutdown, venezuela-crisis, strait-of-hormuz, 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, disaster-event-atlantic-hurricane, rate-decision-interest-rates-irs, funding-round-perplexity, economic-indicator-unemployment, election-michael, election-republican-republicans, election-alabama-republican, election-arkansas-republican, election-florida-republican, election-georgia-republican, election-kansas-republican, election-michigan-republican, funding-round-spacex, regulatory-action-congress, election-republican, election-scott, ceasefire-peace-iran, election-alaska, election-alaska-senate, election-darline-graham-graham, election-darline-graham-republican, election-democratic-party-massachusetts, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, product-launch-xai, funding-round-stripe, election-germany, product-launch-anthropic-claude-opus, election-israel, election-democrat-democrats, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-brazil-senate, election-chen, election-democratic-party, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-russia, election-democratic-party-senate, election-democratic-party-swedish, election-france-senate, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-michigan-senate)"get_truth_object1 field changedInput schema / properties / topic / descriptionPrevious value: -"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, brazil-election, us-midterms-2026, us-presidential-2028, venezuela-crisis, strait-of-hormuz, us-government-shutdown, 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, rate-decision-interest-rates-irs, funding-round-perplexity, election-michael, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-darline-graham-graham, election-darline-graham-republican, election-democratic-party-massachusetts, election-georgia-republican, election-minnesota-republican, election-minnesota-senate, election-nebraska-republican, election-republican, election-scott, ceasefire-peace-iran, election-brazil-senate, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-senate, election-florida-republican, election-france-senate, election-kansas-republican, election-michigan-republican, election-michigan-senate, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, product-launch-xai, funding-round-stripe, election-germany, product-launch-anthropic-claude-opus, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-chen, election-democratic-party, election-democratic-party-russia, election-democratic-party-swedish, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-national-assembly)"New value: +"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, us-midterms-2026, us-presidential-2028, brazil-election, us-government-shutdown, venezuela-crisis, strait-of-hormuz, 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, disaster-event-atlantic-hurricane, rate-decision-interest-rates-irs, funding-round-perplexity, election-michael, election-republican-republicans, election-alabama-republican, election-arkansas-republican, election-florida-republican, election-georgia-republican, election-kansas-republican, election-michigan-republican, funding-round-spacex, regulatory-action-congress, election-republican, election-scott, ceasefire-peace-iran, election-alaska, election-alaska-senate, election-darline-graham-graham, election-darline-graham-republican, election-democratic-party-massachusetts, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, product-launch-xai, funding-round-stripe, election-germany, product-launch-anthropic-claude-opus, election-israel, economic-indicator-unemployment, election-democrat-democrats, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-brazil-senate, election-chen, election-democratic-party, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-russia, election-democratic-party-senate, election-democratic-party-swedish, election-france-senate, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-michigan-senate)"get_truth_object1 field changedInput schema / properties / topic / descriptionPrevious value: -"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, us-presidential-2028, brazil-election, us-midterms-2026, venezuela-crisis, strait-of-hormuz, us-government-shutdown, 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, rate-decision-interest-rates-irs, funding-round-perplexity, election-michael, election-minnesota-republican, election-republican, election-scott, ceasefire-peace-iran, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-darline-graham-graham, election-darline-graham-republican, election-democratic-party-massachusetts, election-florida-republican, election-georgia-republican, election-kansas-republican, election-michigan-republican, election-minnesota-senate, election-nebraska-republican, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, product-launch-xai, funding-round-stripe, election-germany, product-launch-anthropic-claude-opus, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-brazil-senate, election-chen, election-democratic-party, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-russia, election-democratic-party-senate, election-democratic-party-swedish, election-france-senate, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-michigan-senate, election-national-assembly)"New value: +"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, brazil-election, us-midterms-2026, us-presidential-2028, venezuela-crisis, strait-of-hormuz, us-government-shutdown, 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, rate-decision-interest-rates-irs, funding-round-perplexity, election-michael, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-darline-graham-graham, election-darline-graham-republican, election-democratic-party-massachusetts, election-georgia-republican, election-minnesota-republican, election-minnesota-senate, election-nebraska-republican, election-republican, election-scott, ceasefire-peace-iran, election-brazil-senate, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-senate, election-florida-republican, election-france-senate, election-kansas-republican, election-michigan-republican, election-michigan-senate, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, product-launch-xai, funding-round-stripe, election-germany, product-launch-anthropic-claude-opus, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-chen, election-democratic-party, election-democratic-party-russia, election-democratic-party-swedish, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-national-assembly)"get_truth_object1 field changedInput schema / properties / topic / descriptionPrevious value: -"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, brazil-election, us-midterms-2026, us-presidential-2028, venezuela-crisis, strait-of-hormuz, us-government-shutdown, 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, rate-decision-interest-rates-irs, funding-round-perplexity, election-michael, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-darline-graham-graham, election-darline-graham-republican, election-democratic-party-massachusetts, election-georgia-republican, election-minnesota-republican, election-minnesota-senate, election-nebraska-republican, election-republican, election-scott, ceasefire-peace-iran, election-brazil-senate, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-senate, election-florida-republican, election-france-senate, election-kansas-republican, election-michigan-republican, election-michigan-senate, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, product-launch-xai, funding-round-stripe, election-germany, product-launch-anthropic-claude-opus, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-chen, election-democratic-party, election-democratic-party-russia, election-democratic-party-swedish, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-national-assembly)"New value: +"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, us-presidential-2028, brazil-election, us-midterms-2026, venezuela-crisis, strait-of-hormuz, us-government-shutdown, 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, rate-decision-interest-rates-irs, funding-round-perplexity, election-michael, election-minnesota-republican, election-republican, election-scott, ceasefire-peace-iran, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-darline-graham-graham, election-darline-graham-republican, election-democratic-party-massachusetts, election-florida-republican, election-georgia-republican, election-kansas-republican, election-michigan-republican, election-minnesota-senate, election-nebraska-republican, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, product-launch-xai, funding-round-stripe, election-germany, product-launch-anthropic-claude-opus, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-brazil-senate, election-chen, election-democratic-party, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-russia, election-democratic-party-senate, election-democratic-party-swedish, election-france-senate, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-michigan-senate, election-national-assembly)"get_truth_object1 field changedInput schema / properties / topic / descriptionPrevious value: -"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, russia-ukraine-war, israel-iran-conflict, gaza-ceasefire, brazil-election, us-midterms-2026, us-presidential-2028, venezuela-crisis, strait-of-hormuz, us-government-shutdown, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, disaster-event-hurricane, funding-round-perplexity, election-michael, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-darline-graham-graham, election-darline-graham-republican, election-democratic-party-massachusetts, election-georgia-republican, election-minnesota-republican, election-minnesota-senate, election-nebraska-republican, rate-decision-interest-rates, election-republican, election-scott, ceasefire-peace-iran, election-brazil-senate, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-senate, election-florida-republican, election-france-senate, election-kansas-republican, election-michigan-republican, election-michigan-senate, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, product-launch-xai, funding-round-stripe, election-germany, product-launch-anthropic-claude-opus, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-chen, election-democratic-party, election-democratic-party-russia, election-democratic-party-swedish, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-national-assembly)"New value: +"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, brazil-election, us-midterms-2026, us-presidential-2028, venezuela-crisis, strait-of-hormuz, us-government-shutdown, 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, rate-decision-interest-rates-irs, funding-round-perplexity, election-michael, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-darline-graham-graham, election-darline-graham-republican, election-democratic-party-massachusetts, election-georgia-republican, election-minnesota-republican, election-minnesota-senate, election-nebraska-republican, election-republican, election-scott, ceasefire-peace-iran, election-brazil-senate, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-senate, election-florida-republican, election-france-senate, election-kansas-republican, election-michigan-republican, election-michigan-senate, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, product-launch-xai, funding-round-stripe, election-germany, product-launch-anthropic-claude-opus, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-chen, election-democratic-party, election-democratic-party-russia, election-democratic-party-swedish, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-national-assembly)"get_truth_object1 field changedInput schema / properties / topic / descriptionPrevious value: -"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, us-government-shutdown, brazil-election, us-presidential-2028, us-midterms-2026, venezuela-crisis, strait-of-hormuz, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, disaster-event-hurricane, election-darline-graham-graham, election-darline-graham-republican, funding-round-perplexity, election-michael, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-democratic-party-massachusetts, election-georgia-republican, election-minnesota-republican, election-minnesota-senate, legal-ruling-supreme-court, election-republican, election-scott, ceasefire-peace-iran, election-brazil-senate, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-senate, election-florida-republican, election-france-senate, election-kansas-republican, election-michigan-republican, election-michigan-senate, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, rate-decision-interest-rates, product-launch-anthropic, funding-round-stripe, product-launch-xai, election-germany, product-launch-anthropic-claude-opus, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-chen, election-democratic-party, election-democratic-party-russia, election-democratic-party-swedish, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-national-assembly)"New value: +"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, russia-ukraine-war, israel-iran-conflict, gaza-ceasefire, brazil-election, us-midterms-2026, us-presidential-2028, venezuela-crisis, strait-of-hormuz, us-government-shutdown, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, disaster-event-hurricane, funding-round-perplexity, election-michael, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-darline-graham-graham, election-darline-graham-republican, election-democratic-party-massachusetts, election-georgia-republican, election-minnesota-republican, election-minnesota-senate, election-nebraska-republican, rate-decision-interest-rates, election-republican, election-scott, ceasefire-peace-iran, election-brazil-senate, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-senate, election-florida-republican, election-france-senate, election-kansas-republican, election-michigan-republican, election-michigan-senate, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, product-launch-xai, funding-round-stripe, election-germany, product-launch-anthropic-claude-opus, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-chen, election-democratic-party, election-democratic-party-russia, election-democratic-party-swedish, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-national-assembly)"get_truth_object1 field changedInput schema / properties / topic / descriptionPrevious value: -"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, us-government-shutdown, us-presidential-2028, brazil-election, us-midterms-2026, venezuela-crisis, strait-of-hormuz, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, disaster-event-hurricane, funding-round-perplexity, election-michael, election-darline-graham-graham, election-darline-graham-republican, election-minnesota-republican, legal-ruling-supreme-court, election-republican, election-scott, ceasefire-peace-iran, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-democratic-party-massachusetts, election-florida-republican, election-georgia-republican, election-kansas-republican, election-michigan-republican, election-minnesota-senate, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, rate-decision-interest-rates, product-launch-anthropic, funding-round-stripe, product-launch-xai, election-germany, product-launch-anthropic-claude-opus, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-brazil-senate, election-chen, election-democratic-party, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-russia, election-democratic-party-senate, election-democratic-party-swedish, election-france-senate, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-michigan-senate, election-national-assembly)"New value: +"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, us-government-shutdown, brazil-election, us-presidential-2028, us-midterms-2026, venezuela-crisis, strait-of-hormuz, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, disaster-event-hurricane, election-darline-graham-graham, election-darline-graham-republican, funding-round-perplexity, election-michael, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-democratic-party-massachusetts, election-georgia-republican, election-minnesota-republican, election-minnesota-senate, legal-ruling-supreme-court, election-republican, election-scott, ceasefire-peace-iran, election-brazil-senate, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-senate, election-florida-republican, election-france-senate, election-kansas-republican, election-michigan-republican, election-michigan-senate, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, rate-decision-interest-rates, product-launch-anthropic, funding-round-stripe, product-launch-xai, election-germany, product-launch-anthropic-claude-opus, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-chen, election-democratic-party, election-democratic-party-russia, election-democratic-party-swedish, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-national-assembly)"get_truth_object1 field changedInput schema / properties / topic / descriptionPrevious value: -"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, us-government-shutdown, brazil-election, us-presidential-2028, us-midterms-2026, venezuela-crisis, strait-of-hormuz, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, disaster-event-hurricane, election-darline-graham-graham, election-darline-graham-republican, funding-round-perplexity, election-michael, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-democratic-party-massachusetts, election-georgia-republican, election-minnesota-republican, election-minnesota-senate, legal-ruling-supreme-court, election-republican, election-scott, ceasefire-peace-iran, election-brazil-senate, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-senate, election-florida-republican, election-france-senate, election-kansas-republican, election-michigan-republican, election-michigan-senate, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, rate-decision-interest-rates, product-launch-anthropic, funding-round-stripe, product-launch-xai, election-germany, product-launch-anthropic-claude-opus, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-chen, election-democratic-party, election-democratic-party-russia, election-democratic-party-swedish, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-national-assembly)"New value: +"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, us-government-shutdown, us-presidential-2028, brazil-election, us-midterms-2026, venezuela-crisis, strait-of-hormuz, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, disaster-event-hurricane, funding-round-perplexity, election-michael, election-darline-graham-graham, election-darline-graham-republican, election-minnesota-republican, legal-ruling-supreme-court, election-republican, election-scott, ceasefire-peace-iran, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-democratic-party-massachusetts, election-florida-republican, election-georgia-republican, election-kansas-republican, election-michigan-republican, election-minnesota-senate, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, rate-decision-interest-rates, product-launch-anthropic, funding-round-stripe, product-launch-xai, election-germany, product-launch-anthropic-claude-opus, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-brazil-senate, election-chen, election-democratic-party, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-russia, election-democratic-party-senate, election-democratic-party-swedish, election-france-senate, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-michigan-senate, election-national-assembly)"get_truth_object1 field changedInput schema / properties / topic / descriptionPrevious value: -"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, us-government-shutdown, brazil-election, us-presidential-2028, us-midterms-2026, venezuela-crisis, strait-of-hormuz, 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, election-darline-graham-graham, election-darline-graham-republican, rate-decision-interest-rates-irs, funding-round-perplexity, election-michael, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-democratic-party-massachusetts, election-georgia-republican, election-minnesota-republican, election-minnesota-senate, legal-ruling-supreme-court, election-republican, election-scott, ceasefire-peace-iran, election-brazil-senate, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-senate, election-florida-republican, election-france-senate, election-kansas-republican, election-michigan-republican, election-michigan-senate, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, funding-round-stripe, product-launch-xai, election-germany, product-launch-anthropic-claude-opus, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-chen, election-democratic-party, election-democratic-party-russia, election-democratic-party-swedish, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-national-assembly)"New value: +"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, us-government-shutdown, brazil-election, us-presidential-2028, us-midterms-2026, venezuela-crisis, strait-of-hormuz, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, disaster-event-hurricane, election-darline-graham-graham, election-darline-graham-republican, funding-round-perplexity, election-michael, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-democratic-party-massachusetts, election-georgia-republican, election-minnesota-republican, election-minnesota-senate, legal-ruling-supreme-court, election-republican, election-scott, ceasefire-peace-iran, election-brazil-senate, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-senate, election-florida-republican, election-france-senate, election-kansas-republican, election-michigan-republican, election-michigan-senate, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, rate-decision-interest-rates, product-launch-anthropic, funding-round-stripe, product-launch-xai, election-germany, product-launch-anthropic-claude-opus, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-chen, election-democratic-party, election-democratic-party-russia, election-democratic-party-swedish, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-national-assembly)"get_truth_object1 field changedInput schema / properties / topic / descriptionPrevious value: -"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, brazil-election, us-midterms-2026, us-presidential-2028, venezuela-crisis, strait-of-hormuz, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, rate-decision-interest-rates, rate-decision-interest-rates-irs, disaster-event-hurricane, funding-round-perplexity, election-darline-graham-graham, election-minnesota-republican, legal-ruling-supreme-court, election-republican, election-scott, ceasefire-peace-iran, election-michael, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-florida-republican, election-georgia-republican, election-kansas-republican, election-michigan-republican, election-minnesota-senate, election-nebraska-republican, election-oklahoma, election-oklahoma-republican, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, funding-round-stripe, product-launch-xai, product-launch-anthropic-claude-opus, election-germany, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-brazil-senate, election-chen, election-democratic-party, 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-democratic-party-swedish, election-france-senate, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-michigan-senate, election-national-assembly, election-ontario)"New value: +"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, us-government-shutdown, brazil-election, us-presidential-2028, us-midterms-2026, venezuela-crisis, strait-of-hormuz, 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, election-darline-graham-graham, election-darline-graham-republican, rate-decision-interest-rates-irs, funding-round-perplexity, election-michael, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-democratic-party-massachusetts, election-georgia-republican, election-minnesota-republican, election-minnesota-senate, legal-ruling-supreme-court, election-republican, election-scott, ceasefire-peace-iran, election-brazil-senate, election-democratic-party-georgia, election-democratic-party-iceland, election-democratic-party-illinois, election-democratic-party-mexico, election-democratic-party-michigan, election-democratic-party-oregon, election-democratic-party-senate, election-florida-republican, election-france-senate, election-kansas-republican, election-michigan-republican, election-michigan-senate, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, funding-round-stripe, product-launch-xai, election-germany, product-launch-anthropic-claude-opus, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-chen, election-democratic-party, election-democratic-party-russia, election-democratic-party-swedish, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-national-assembly)"get_truth_object1 field changedInput schema / properties / topic / descriptionPrevious value: -"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, brazil-election, us-midterms-2026, us-presidential-2028, venezuela-crisis, strait-of-hormuz, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, rate-decision-interest-rates, election-darline-graham-graham, rate-decision-interest-rates-irs, disaster-event-hurricane, funding-round-perplexity, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-georgia-republican, election-minnesota-republican, election-minnesota-senate, election-nebraska-republican, election-oklahoma-republican, legal-ruling-supreme-court, election-republican, election-scott, ceasefire-peace-iran, election-michael, 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-florida-republican, election-france-senate, election-kansas-republican, election-michigan-republican, election-michigan-senate, election-oklahoma, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, funding-round-stripe, product-launch-xai, product-launch-anthropic-claude-opus, election-germany, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, 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-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-national-assembly, election-ontario)"New value: +"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, brazil-election, us-midterms-2026, us-presidential-2028, venezuela-crisis, strait-of-hormuz, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, rate-decision-interest-rates, rate-decision-interest-rates-irs, disaster-event-hurricane, funding-round-perplexity, election-darline-graham-graham, election-minnesota-republican, legal-ruling-supreme-court, election-republican, election-scott, ceasefire-peace-iran, election-michael, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-florida-republican, election-georgia-republican, election-kansas-republican, election-michigan-republican, election-minnesota-senate, election-nebraska-republican, election-oklahoma, election-oklahoma-republican, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, funding-round-stripe, product-launch-xai, product-launch-anthropic-claude-opus, election-germany, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-brazil-senate, election-chen, election-democratic-party, 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-democratic-party-swedish, election-france-senate, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-michigan-senate, election-national-assembly, election-ontario)"get_truth_object1 field changedInput schema / properties / topic / descriptionPrevious value: -"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, brazil-election, us-midterms-2026, us-presidential-2028, venezuela-crisis, strait-of-hormuz, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, rate-decision-interest-rates, rate-decision-interest-rates-irs, disaster-event-hurricane, funding-round-perplexity, election-darline-graham-graham, election-minnesota-republican, legal-ruling-supreme-court, election-republican, election-scott, ceasefire-peace-iran, election-michael, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-florida-republican, election-georgia-republican, election-kansas-republican, election-michigan-republican, election-minnesota-senate, election-nebraska-republican, election-oklahoma, election-oklahoma-republican, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, funding-round-stripe, product-launch-xai, product-launch-anthropic-claude-opus, election-germany, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-brazil-senate, election-chen, election-democratic-party, 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-democratic-party-swedish, election-france-senate, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-michigan-senate, election-national-assembly, election-ontario)"New value: +"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, brazil-election, us-midterms-2026, us-presidential-2028, venezuela-crisis, strait-of-hormuz, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, rate-decision-interest-rates, election-darline-graham-graham, rate-decision-interest-rates-irs, disaster-event-hurricane, funding-round-perplexity, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-georgia-republican, election-minnesota-republican, election-minnesota-senate, election-nebraska-republican, election-oklahoma-republican, legal-ruling-supreme-court, election-republican, election-scott, ceasefire-peace-iran, election-michael, 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-florida-republican, election-france-senate, election-kansas-republican, election-michigan-republican, election-michigan-senate, election-oklahoma, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, funding-round-stripe, product-launch-xai, product-launch-anthropic-claude-opus, election-germany, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, 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-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-national-assembly, election-ontario)"get_truth_object1 field changedInput schema / properties / topic / descriptionPrevious value: -"Which 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, venezuela-crisis, strait-of-hormuz, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, rate-decision-interest-rates, election-darline-graham-graham, rate-decision-interest-rates-irs, disaster-event-hurricane, funding-round-perplexity, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-georgia-republican, election-minnesota-republican, election-minnesota-senate, election-nebraska-republican, election-oklahoma-republican, legal-ruling-supreme-court, election-republican, election-scott, ceasefire-peace-iran, election-michael, 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-florida-republican, election-france-senate, election-kansas-republican, election-michigan-republican, election-michigan-senate, election-oklahoma, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, funding-round-stripe, product-launch-xai, product-launch-anthropic-claude-opus, election-germany, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, 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-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-national-assembly, election-ontario)"New value: +"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, brazil-election, us-midterms-2026, us-presidential-2028, venezuela-crisis, strait-of-hormuz, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, rate-decision-interest-rates, rate-decision-interest-rates-irs, disaster-event-hurricane, funding-round-perplexity, election-darline-graham-graham, election-minnesota-republican, legal-ruling-supreme-court, election-republican, election-scott, ceasefire-peace-iran, election-michael, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-florida-republican, election-georgia-republican, election-kansas-republican, election-michigan-republican, election-minnesota-senate, election-nebraska-republican, election-oklahoma, election-oklahoma-republican, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, funding-round-stripe, product-launch-xai, product-launch-anthropic-claude-opus, election-germany, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-brazil, election-brazil-senate, election-chen, election-democratic-party, 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-democratic-party-swedish, election-france-senate, election-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-michigan-senate, election-national-assembly, election-ontario)"get_truth_object1 field changedInput schema / properties / topic / descriptionPrevious value: -"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, gaza-ceasefire, russia-ukraine-war, brazil-election, us-midterms-2026, us-presidential-2028, venezuela-crisis, strait-of-hormuz, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, rate-decision-interest-rates, rate-decision-interest-rates-irs, disaster-event-hurricane, funding-round-perplexity, legal-ruling-supreme-court, ceasefire-peace-iran, election-alaska, election-alaska-senate, election-darline-graham-graham, election-minnesota-republican, election-minnesota-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-israel, election-michael, funding-round-kraken, price-threshold-nvidia, election-republican-republicans, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-alabama-republican, election-arkansas-republican, election-brazil, election-brazil-senate, election-chen, election-democratic-party, 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-democratic-party-swedish, election-florida-republican, election-france-senate, election-georgia-republican, election-hamilton, election-hannover, election-hong-wisconsin, election-kansas-republican, election-lebanon, election-mexico, election-michigan, election-michigan-republican, election-michigan-senate, election-national-assembly, election-nebraska-republican, election-oklahoma, election-oklahoma-republican, election-ontario)"New value: +"Which 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, venezuela-crisis, strait-of-hormuz, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, rate-decision-interest-rates, election-darline-graham-graham, rate-decision-interest-rates-irs, disaster-event-hurricane, funding-round-perplexity, election-republican-republicans, election-alabama-republican, election-alaska, election-alaska-senate, election-arkansas-republican, election-georgia-republican, election-minnesota-republican, election-minnesota-senate, election-nebraska-republican, election-oklahoma-republican, legal-ruling-supreme-court, election-republican, election-scott, ceasefire-peace-iran, election-michael, 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-florida-republican, election-france-senate, election-kansas-republican, election-michigan-republican, election-michigan-senate, election-oklahoma, funding-round-spacex, economic-indicator-inflation, bitcoin-price-level, election-france, product-launch-anthropic, funding-round-stripe, product-launch-xai, product-launch-anthropic-claude-opus, election-germany, election-democrat-democrats, election-israel, funding-round-kraken, price-threshold-nvidia, election-swedish, 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-hamilton, election-hannover, election-hong-wisconsin, election-lebanon, election-mexico, election-michigan, election-national-assembly, election-ontario)"get_truth_object1 field changedInput schema / properties / topic / descriptionPrevious value: -"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, brazil-election, us-midterms-2026, 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)"New value: +"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, gaza-ceasefire, russia-ukraine-war, brazil-election, us-midterms-2026, us-presidential-2028, venezuela-crisis, strait-of-hormuz, fed-rate-decision, uk-election, us-recession-2026, disaster-event-earthquake, product-launch-spacex, product-launch-spacex-starlink, rate-decision-interest-rates, rate-decision-interest-rates-irs, disaster-event-hurricane, funding-round-perplexity, legal-ruling-supreme-court, ceasefire-peace-iran, election-alaska, election-alaska-senate, election-darline-graham-graham, election-minnesota-republican, election-minnesota-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-israel, election-michael, funding-round-kraken, price-threshold-nvidia, election-republican-republicans, election-swedish, economic-indicator-cpi, economic-indicator-cpi-japan, economic-indicator-gdp, economic-indicator-gdp-japan, election-alabama-republican, election-arkansas-republican, election-brazil, election-brazil-senate, election-chen, election-democratic-party, 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-democratic-party-swedish, election-florida-republican, election-france-senate, election-georgia-republican, election-hamilton, election-hannover, election-hong-wisconsin, election-kansas-republican, election-lebanon, election-mexico, election-michigan, election-michigan-republican, election-michigan-senate, election-national-assembly, election-nebraska-republican, election-oklahoma, election-oklahoma-republican, election-ontario)"get_truth_object1 field changedInput schema / properties / topic / descriptionPrevious value: -"Which 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)"New value: +"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, brazil-election, us-midterms-2026, 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)"get_truth_object1 field changedInput schema / properties / topic / descriptionPrevious value: -"Which truth object (default \"hormuz\" — published: hormuz, interest-rates, ai-model-race, israel-iran-conflict, russia-ukraine-war, gaza-ceasefire, brazil-election, us-midterms-2026, 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)"New value: +"Which 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)"Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Bitcoin-anchored, tamper-evident audit log for AI agents — record, disclose and verify actions.
Machine-readable entity discovery with provenance, trust and verified source evidence.
Immutable event logging and audit trail for agent transactions
Bitcoin-anchored, tamper-evident audit-permanence layer for AI agents, FRE 902(13)/(14)-shaped.
Add one secure layer between your agents and this server.
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.
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.
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.
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.