Skip to main content
Glama
psxdata-mcp

psxdata-mcp

by psxdata

load_screener

Load the full PSX screener (~750 symbols: sector, price, market cap, P/E, dividend yield, free float, 30-day avg volume, 1-year change, traded_today, ex_flag) into table screener. 15-min snapshot.

Instructions

Load the full PSX screener (~750 symbols: sector, price, market cap, P/E, dividend yield, free float, 30-day avg volume, 1-year change, traded_today, ex_flag) into table screener. 15-min snapshot. See traded_today and ex_flag in the server instructions — filter on them before ranking daily moves.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the payload size (~750 symbols), the destination table, the 15-minute snapshot freshness, and the exact columns written. It stops short of stating whether the load overwrites existing rows in `screener`, how long it takes, or whether it hits the network.

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

Conciseness5/5

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

Three dense sentences, front-loaded with the action and scope, then freshness, then the caveat about traded_today/ex_flag. The parenthetical column list is compact and every clause carries information an agent needs.

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 no-parameter loader with an output schema already defined, the description covers what is loaded, where it lands, how fresh it is, and the key data-quality gotchas. It leaves only idempotency/overwrite behavior and execution cost unstated — gaps that are unlikely to change how an agent calls it.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description instead spends its words on the data payload, which is the relevant 'input' context here.

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 description opens with a specific verb and resource ('Load the full PSX screener') and quantifies scope (~750 symbols) plus the destination table `screener`. It is immediately clear this bulk-populates a screener table rather than fetching quotes or prices, though it never names a sibling alternative to sharpen the distinction.

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?

It gives downstream usage guidance — filter on traded_today and ex_flag before ranking daily moves — and defers to server instructions for those flags. However, it never says when to call this versus load_prices, load_fundamentals, or quote, nor any prerequisite or refresh cadence beyond the 15-min snapshot note.

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