Skip to main content
Glama
Sign In

Kr Equities

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Kr Quote

kr_quote
Read-onlyIdempotent

Current or last-close quote for one Korean listed stock by 6-character code: price, change, day range, volume, market cap, 52-week range, PER/PBR/EPS/dividend yield, foreign ownership, and the issuer identity and exchange (KOSPI/KOSDAQ). Returns market_status (OPEN/CLOSE) and the exchange timestamp.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
codeYes6-character Korean stock code, e.g. 005930 (Samsung Electronics), 000660 (SK hynix)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds real value by disclosing the fallback to last close when the market is not open, and by stating that market_status (OPEN/CLOSE) and the exchange timestamp are returned.

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?

Two sentences, front-loaded with the core action and scope before the field enumeration. The long list of returned fields is information-dense rather than wasted, though it could be grouped slightly more tightly.

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?

With a single fully documented parameter and no output schema, the description carries the return-value burden well: it names the quote fields, the exchange identity (KOSPI/KOSDAQ), market_status, and the timestamp. Nothing essential for a correct call is missing.

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 100% and the single 'code' parameter is fully documented with examples (005930, 000660). The description only restates '6-character code' and adds no format or validation detail beyond the schema, so the baseline of 3 applies.

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 and resource ('quote for one Korean listed stock by 6-character code') and enumerates exactly what the quote covers. That scope (single stock, current/last-close snapshot) implicitly separates it from kr_price_history, kr_index, kr_top_by_market_cap, and kr_search_stocks.

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 'current or last-close' framing implies when the tool applies, but there is no explicit guidance on when to prefer it over siblings like kr_price_history or kr_search_stocks. The agent must infer that this is the single-symbol snapshot tool.

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

All Kr Equities toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources