pse-edge-mcp

Overview Schema Source Related Servers Discussions Admin

Price history (OHLC)

get_price_history

Read-only

Retrieve daily OHLC price history for Philippine Stock Exchange (PSE) symbols. Specify custom date ranges or use the default last six months of end-of-day data.

Instructions

Get daily OHLC price history for a PSE stock symbol.

Dates are ISO format (YYYY-MM-DD). Defaults to the last ~6 months. Data comes from PSE Edge's own chart endpoint and is EOD-frozen. If the market is open and this exact range has never been cached, a one-time fetch may include today's still-moving bar, flagged stale=true with an explanatory meta.note.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_price_history"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes
`end_date`	No
`start_date`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.0Aug 1, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description adds valuable behavioral details: the data is EOD-frozen from PSE Edge's chart endpoint, and a one-time fetch may include a live bar flagged stale=true with an explanatory meta.note. This discloses caching and freshness behavior not captured by annotations.

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?

The description is compact and front-loaded: a one-sentence purpose, followed by a terse paragraph of relevant details. Every sentence adds value—date format, default window, data source, staleness caveat—with no redundancy.

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?

The tool has an output schema and simple parameters; the description covers the essential context: data source, time zone or date format, default window, and the stale-bar edge case. This is complete for a read-only historical data tool.

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

Parameters5/5

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

Schema coverage for parameters is 0%, but the description compensates by documenting date format (ISO YYYY-MM-DD), default range (~6 months), and symbol identity (PSE stock symbol). This gives the agent meaning for all three parameters beyond the bare schema.

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?

The description opens with a specific verb-resource statement: 'Get daily OHLC price history for a PSE stock symbol.' This clearly identifies the tool's function and scope, and differentiates it from sibling tools like get_stock_quote (current quote) and search_companies.

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?

The description establishes clear usage context: daily OHLC historical data for PSE symbols, with default date range and ISO format. It does not explicitly name alternative tools or state when not to use it, but the context is sufficient for an agent to select it for historical OHLC requests.

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

Deploy Server