Skip to main content
Glama

Token Command Center

tc_screen

Read-only

Screen the whole Book (all scored tokens) and get compact ranked rows. Filters: lens (long, short, no-edge), verdict (Real, Mid, Theater), tier, category, sector (a clean label such as Lending or Memes), flow_model (comma-separated for several), stale, query; numeric ranges via min/max objects, e.g. {"min": {"health": 60, "arr": 1000000}, "max": {"ps": 20}}. Fields: alerts, arr (annualized revenue, USD), arr_30d (ARR change over 30 days, %), arr_7d (ARR change over 7 days, %), category, conflicts, date, fdv, flow_model, health (0-100 health score, set when the scorecard is written), health_change, holders_rev (annualized revenue to holders, USD), lens (long, short or no-edge), mcap, name, net_flow (holders revenue minus emissions, USD/yr), nf_yield (net flow / market cap, %), pct_unlocked, price, price_frozen_days, ps (market cap / annualized revenue), scorecard_age_days, sector (one clean sector beside the raw category, or null), stale, symbol, tier, unlock_30d (% of supply unlocking in the next 30 days), verdict (value accrual: Real, Mid or Theater). Tokens with no value for a ranged field are excluded, never counted as zero.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tc_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoUpper bounds by numeric field.
minNoLower bounds by numeric field.
lensNo
sortNo
tierNo
limitNo
orderNo
queryNoSubstring of slug, symbol or name.
staleNo
fieldsNo
sectorNo
verdictNo
categoryNo
flow_modelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / fields / items / enum
      Previous value: -[
      -  "alerts",
      -  "arr",
      -  "arr_30d",
      -  "arr_7d",
      -  "category",
      -  "conflicts",
      -  "date",
      -  "fdv",
      -  "flow_model",
      -  "health",
      -  "health_change",
      -  "holders_rev",
      -  "lens",
      -  "mcap",
      -  "name",
      -  "net_flow",
      -  "nf_yield",
      -  "pct_unlocked",
      -  "price",
      -  "price_frozen_days",
      -  "ps",
      -  "scorecard_age_days",
      -  "stale",
      -  "symbol",
      -  "tier",
      -  "unlock_30d",
      -  "verdict"
      -]New value: +[
      +  "alerts",
      +  "arr",
      +  "arr_30d",
      +  "arr_7d",
      +  "category",
      +  "conflicts",
      +  "date",
      +  "fdv",
      +  "flow_model",
      +  "health",
      +  "health_change",
      +  "holders_rev",
      +  "lens",
      +  "mcap",
      +  "name",
      +  "net_flow",
      +  "nf_yield",
      +  "pct_unlocked",
      +  "price",
      +  "price_frozen_days",
      +  "ps",
      +  "scorecard_age_days",
      +  "sector",
      +  "stale",
      +  "symbol",
      +  "tier",
      +  "unlock_30d",
      +  "verdict"
      +]
    • addedInput schema / properties / sector
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / sort / enum
      Previous value: -[
      -  "alerts",
      -  "arr",
      -  "arr_30d",
      -  "arr_7d",
      -  "category",
      -  "conflicts",
      -  "date",
      -  "fdv",
      -  "flow_model",
      -  "health",
      -  "health_change",
      -  "holders_rev",
      -  "lens",
      -  "mcap",
      -  "name",
      -  "net_flow",
      -  "nf_yield",
      -  "pct_unlocked",
      -  "price",
      -  "price_frozen_days",
      -  "ps",
      -  "scorecard_age_days",
      -  "stale",
      -  "symbol",
      -  "tier",
      -  "unlock_30d",
      -  "verdict"
      -]New value: +[
      +  "alerts",
      +  "arr",
      +  "arr_30d",
      +  "arr_7d",
      +  "category",
      +  "conflicts",
      +  "date",
      +  "fdv",
      +  "flow_model",
      +  "health",
      +  "health_change",
      +  "holders_rev",
      +  "lens",
      +  "mcap",
      +  "name",
      +  "net_flow",
      +  "nf_yield",
      +  "pct_unlocked",
      +  "price",
      +  "price_frozen_days",
      +  "ps",
      +  "scorecard_age_days",
      +  "sector",
      +  "stale",
      +  "symbol",
      +  "tier",
      +  "unlock_30d",
      +  "verdict"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: "Tokens with no value for a ranged field are excluded, never counted as zero," and notes that health is "set when the scorecard is written" plus scorecard_age_days/stale as freshness signals. It still does not say what the default row count is or how sorting defaults.

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?

Purpose is front-loaded and the filter list precedes the field glossary, which is the right order. But the field glossary is a dense run-on, and lens ("long, short, no-edge") and verdict ("Real, Mid, Theater") are each defined twice — once in the filter list and again in the fields list — which is wasted space.

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

Completeness4/5

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

For a 14-parameter tool with no output schema and thin schema descriptions, the definition covers the domain vocabulary well enough to call the tool correctly. It is slightly incomplete on pagination/sort defaults and on what "compact" means when the fields parameter is omitted, but nothing critical is missing.

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 only 21%, so the description must carry the load, and it largely does: it defines units and meaning for many fields (arr = annualized revenue USD, nf_yield = net flow / market cap %, ps = mcap / revenue, unlock_30d = % of supply unlocking in 30 days, net_flow = holders revenue minus emissions) and shows a concrete min/max object example. Gaps remain for sort, order and limit, which are only constrained by the schema enum and 1-50 bounds.

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?

States a specific verb and scope: "Screen the whole Book (all scored tokens) and get compact ranked rows," which tells an agent this is a bulk-screening read over the full token universe rather than a single lookup. It does not explicitly name a sibling (e.g. tc_search_tokens or tc_list_tokens) as the alternative for name-based lookup, so differentiation is inferable rather than stated.

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 description enumerates the filter vocabulary (lens, verdict, tier, category, sector, flow_model, stale, query, min/max) which implies the intended use case: narrowing the Book by scorecard attributes. However it never says when to prefer this tool over tc_list_tokens, tc_search_tokens or tc_get_token, and gives no exclusions or preconditions.

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