Skip to main content
Glama

Get your facts on a ticker and what each did

get_gambit_facts
Read-onlyIdempotent

YOUR facts on one ticker and what each did to your own view (requires api:read) — the call for "what have I added on INIT?" or before removing one. The chain for one ticker. Everything it stores is in YOUR personal layer: the shared view never changes because of it. Gambit forms your view on its side: you do not need your own model for it. (1) Add data: add_gambit_evidence stores a fact you know. It is labelled unconfirmed until Gambit confirms it from an official or wire source that states it; a confirmed fact's source joins the shared evidence, and the shared view uses it on its normal run. (2) Your view: your own take, which Gambit keeps for you. It starts as the shared take. Each fact you add, each new shared version and each update you ask for moves it: Gambit's per-story step judges your new facts and the shared news since your last update against your take and applies its verdicts. A fact that changes a lever adds a test to your take: wrong if the fact is not confirmed by its check-by date. A fact that expires unconfirmed after its check-by date leaves no trace: when Gambit had set it aside (it moved nothing), your view stays as it is; otherwise your take points back to the shared take and Gambit applies your remaining facts again on it, and with no fact left you follow the shared view. remove_gambit_evidence takes one fact back; reset_gambit_view takes back every fact. When your take ends up the same as the shared one, you follow the shared view again. To use your own model's view instead (optional): call get_gambit_pack, form the take with the rules and output_schema in the pack, then call submit_gambit_view; Gambit then moves that view the same way. (3) What if: what_if_gambit gives the view if something happened; when the question matches a dated condition the view already lists, the answer is precomputed and no model runs; otherwise it returns the pack with the event added, for your model to answer. (4) Plan: plan_gambit gives entry, stop, size and exits from your own limits. A plan is not a recommendation to trade and places no order. Returns facts: your active facts (unconfirmed or confirmed; expired and removed ones are not listed), the newest 50, oldest first, each with user_item_id (pass it to remove_gambit_evidence), claim, url, status, created_at, check_by, effect (what it last did: effect, target and target_name, the lever it moved or was set aside from, direction, set_aside_reason, and lean_move when it moved your view; null before Gambit has stepped it) and filing (the SEC filing passage the fact cites: company, form, filed, quote, source_url, status confirmed or sourced; null when it cites none); and follows (own when your view is your own, gambit when it is Gambit's). A fact the per-item step logged as a new lever has not moved your view yet: it waits for a full review. Errors: 409 gambit_building when Gambit has no view of the ticker yet (get_gambit by symbol queues it; try again later); 404 unknown_symbol; 422 ambiguous_symbol with candidates (call again with one candidate as the symbol); 503 gambit_personal_disabled while the personal layer is switched off. Gambit runs no model for this call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_gambit_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesa ticker such as BTC or NVDA, or an exact id such as xyz:GOOGL or ref:eq:IP, as for get_gambit

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say read-only and idempotent; the description adds real behavior: everything stays in the caller's personal layer, the shared view is never changed, no model runs for this call, facts are capped at the newest 50 oldest-first, expired and removed facts are omitted, and it enumerates the 409/404/422/503 error modes with recovery actions. That is context an agent cannot get from the annotations.

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

Conciseness3/5

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

Front-loaded with the purpose and the listing behavior, but the middle is bloated with the mechanics of the wider Gambit system (confirmation lifecycle, per-story stepping, check-by expiry, what-if precomputation, plan generation) that belong to the sibling tools cited rather than to this read call. Returns and errors are placed at the end where they are useful, but the definition could be half the length without losing selection guidance.

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

Completeness5/5

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

There is no output schema, and the description compensates by enumerating the returned fields (user_item_id, claim, url, status, created_at, check_by, effect with its sub-fields, filing, follows) and the error envelopes. For a complex read tool that also has to explain why an expected fact may be missing, nothing an agent needs to call it correctly is absent.

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

Parameters4/5

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

Schema coverage is 100%, so the single symbol parameter is already documented, and the description mostly says 'as for get_gambit'. It does add one piece of meaning the schema lacks: the 422 ambiguous_symbol response carries candidates, and the caller should re-invoke with a chosen candidate as the symbol, which changes how the parameter is used on retry.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('YOUR facts on one ticker and what each did to your own view') and immediately distinguishes itself from add_gambit_evidence and remove_gambit_evidence: this lists, those mutate. An agent can select it without opening the schema.

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

Usage Guidelines5/5

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

Gives concrete triggers ('what have I added on INIT?', 'before removing one') and names the alternatives for adjacent intents: add_gambit_evidence to store, remove_gambit_evidence for one fact, reset_gambit_view for all, get_gambit_pack plus submit_gambit_view for a custom model. When-to-use and when-to-use-something-else are both explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources