Skip to main content
Glama

Get a theme with its members and history

get_theme
Read-onlyIdempotent

One of YOUR themes in full. A theme is a named group of tickers with attribution. kind rule: the user's own words (rule_text), compiled once per save or edit into a ranked list. Tracked tickers (at most tracked_cap, at most 10: a theme never opens more than 10 Gambits) open a follow: each is followed as an ordinary Gambit, so it gets Gambit's take. They are chosen when the theme is saved, edited or activated, in this order: tickers the user added by hand or named in the rule (added_by user), then tickers with the most recent event in the last 7 days (an opportunity card or a news item on it), ties by rank. A member's tracked_by says why it is tracked. The rest, up to watched_cap, are watched: listed with their reason, no Gambit. Tiers do not move between those moments. kind manual: tickers the user adds by hand, tracked up to tracked_cap and watched past it. A Gambit the theme opened becomes the user's own, and no theme stops it, once the user follows that ticker with create_gambit or changes its monitoring. Every member records how it got in (added_by rule, news or user) and why (reason); every change is an event. rule_version counts the compiles of the rule; member_list_version counts the changes of the member list. A draft theme follows nothing; an active one follows its tracked members. Themes never trade. Returns everything list_themes returns, plus members grouped by tier: members.tracked and members.watched, each with subject_id, symbol, added_by (rule | news | user: how it got in), reason (why it is in), tracked_by (for a tracked member, why it is tracked and so followed: named_in_rule, added_by_user, or the card or news event with its id and time), signal (the numbers the compile's ranking saw: r5, r20, r60 returns in percent, volz, dv20_usd_m, cards7, news7, and bars, the price source; a missing number means no data), tradable (true when it has a Hyperliquid listing; without one it can only be watched for trading), case_id (the Gambit this theme opened for a tracked member; null when the user already followed the ticker or it is watched), rank (its place in the latest compile), joined_at and updated_at. events: the last 50 changes, newest first, each with kind (created, compiled, edited, activated, paused, archived, joined, left, promoted, demoted), subject_id and symbol (for a member change), added_by (who caused it: rule, news or user), reason, the rule_version and member_list_version after it, payload (for example what happened to the member's Gambit: opened, resumed, already_followed, stopped or handed_over to another theme) and created_at. Cite a theme as theme_id + rule_version + member_list_version. Errors: 404 theme_not_found (not yours, or no such theme); 503 themes_disabled. (Requires api:read.)

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": {
      "theme_id": "<theme_id>"
    },
    "name": "get_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
theme_idYesa theme id from list_themes (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive), and the description adds genuinely non-structured facts: the api:read scope requirement, the 404 theme_not_found semantics ('not yours, or no such theme'), the 503 themes_disabled case, and the last-50-events cap. That is real added behavioral value beyond 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.

Conciseness2/5

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

Roughly 500 words of dense prose for a one-parameter read; the tracked-vs-watched tier mechanics, ranking order and Gambit handover rules occupy most of the text and push the actual return shape far back. There is no structure or front-loading, so an agent must read the whole block to find what it gets back.

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?

With no output schema, the description carries the full burden and does so exhaustively: member fields, tier grouping, event kinds and payloads, version counters, plus error cases and the auth requirement. Nothing an agent needs to interpret the response or handle failure is missing.

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

Parameters3/5

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

With 100% schema coverage on the single theme_id parameter, the schema already documents the UUID source and format. The description adds only the citation convention (theme_id + rule_version + member_list_version), which is marginally useful but not about the parameter's value domain.

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

Purpose4/5

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

The title plus the opening line establish that this fetches a single theme in full, and the closing clause 'Returns everything list_themes returns, plus members grouped by tier' cleanly separates it from the list sibling. The verb is never stated in the description body itself ('One of YOUR themes in full'), so the resource is clearer than the action.

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

Usage Guidelines3/5

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

The relationship to list_themes is stated (this is a superset), which implies you call this once you have a theme_id, but there is no explicit 'use this when… / use save_theme or preview_theme when…' routing. Usage is inferred from the domain exposition rather than stated as a rule.

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