Skip to main content
Glama

Screen the tradable universe

acubic_screen_universe
Read-onlyIdempotent

Applies filter rules (e.g. market cap at least $10 billion, P/E at most 25; AND, up to 20) to the universe eToro and Trading 212 both hold, after optional asset class, region, sector and include narrowing. Returns how many pass, per asset class, with up to 25 example rows, from the latest snapshot (as_of). A stock-only metric passes funds and crypto. To rank names for a strategy use acubic_rank_candidates.

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": "acubic_screen_universe"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size.
orderNoSort direction.desc
cursorNoA previous next_cursor.
localeNoThe language of this conversation.
includeNoIds per acubic_list_strategy_options section (index: indices).
regionsNoNarrow to these regions first.
sectorsNoNarrow to these sectors first.
order_byNoOrder the example rows by this metric.market_cap
filter_rulesNoRules combined with AND.
asset_classesNoNarrow to these asset classes first.
response_formatNoconcise

Output Schema

NameRequiredDescriptionDefault
rowsNo
as_ofNoDate of the data snapshot; null when not reported.
errorNo
countsNo
truncatedNo
disclosureNo
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the bar is lower; the description still adds real value by naming the universe as the intersection of eToro and Trading 212 holdings, the latest-snapshot (as_of) semantics, and the return shape (pass counts per asset class plus up to 25 example rows). The quirk 'A stock-only metric passes funds and crypto' discloses a non-obvious filtering behavior, though it is stated cryptically and could mislead about how funds/crypto are evaluated.

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

Conciseness4/5

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

Four dense sentences, front-loaded with the core action and ending with the sibling routing pointer, which is a sensible place for it. Minor cost: the 'stock-only metric passes funds and crypto' clause is compressed to the point of ambiguity.

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?

An output schema exists and annotations are rich, so the description does not need to explain return values, yet it still summarizes counts, example rows and as_of. For an 11-parameter tool the include object's many sections are left entirely to the schema, which is acceptable given 91% coverage.

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

Parameters3/5

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

Schema coverage is 91%, so the schema already documents nearly every parameter including units and the AND combination of filter_rules. The description adds only a worked example ($10B market cap, P/E ≤25) and the 20-rule cap, which the schema already encodes as maxItems, so it clears the baseline without materially extending parameter meaning.

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 (applies filter rules) and resource (the dual-broker tradable universe), plus scope details: AND-combined rules, max 20, applied after asset class/region/sector/include narrowing. It also distinguishes itself from acubic_rank_candidates, so an agent can route without opening either schema.

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

Usage Guidelines4/5

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

Explicitly routes ranking work to acubic_rank_candidates, which is the key alternative an agent would confuse with screening. It does not state prerequisites or when-not to screen at all, but the screening-vs-ranking split is clear.

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