Skip to main content
Glama

Get Screen

get_screen

Screen the supported symbol universe using the supplied criteria. May persist a calculation job, usage record or saved settings. Successful calculations may consume account allowance. Repeating the request may have side effects.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNo
tickerYes
languageNo
model_idsNo
request_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior4/5

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

The annotations already flag readOnlyHint=false and idempotentHint=false, and the description adds real value on top: it warns that a calculation job, usage record, or saved settings may be persisted, that successful calculation may consume allowance, and that repeats may cause side effects. What is still missing is anything about return shape or expected latency, but for a billable, state-touching operation this is meaningfully more than the annotations provide.

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 short sentences with the action front-loaded, and no filler. The final two sentences about allowance and side effects overlap somewhat, but each conveys a distinct operational risk.

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

Completeness2/5

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

This is a five-parameter, non-idempotent, potentially billable tool with no output schema, and the description neither explains the inputs nor describes what comes back. The cost/side-effect warning is good, but an agent still cannot predict what a screen returns or how to choose model_ids, which is the central decision in calling it.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, and it does not. None of the five parameters (ticker, as_of, language, model_ids, request_id) is named or explained; "the supplied criteria" is the only hint, and the enumeration of model_ids (hot, snapback, bio, spread, lc) — the most consequential input — is left entirely to the schema with no gloss on what those models mean.

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

Purpose3/5

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

It gives a verb and resource ("Screen the supported symbol universe") but leaves the core concept unexplained: what a "screen" actually produces is never stated, and the criteria are only gestured at as "the supplied criteria." Nothing distinguishes it from siblings like get_bench_result, get_house_view, or get_symbol_reports, which could plausibly also filter the symbol universe.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives, and no prerequisites or exclusions. A reader cannot tell whether this is a pre-trade idea-generation screen, a model-ranking screen, or something else, nor when to prefer it over the many analysis siblings.

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