Skip to main content
Glama
zenith-sb-mcp

zenith-sb-mcp

keystats

Read-only

Retrieves key statistics for an IDX-listed company, including valuation, size, and performance metrics, to support stock research and comparison.

Instructions

Key statistics for a company (valuation, size, performance metrics).

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

Input Schema

NameRequiredDescriptionDefault
symbolYesIDX ticker

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that — no note on data freshness, currency/units of the statistics, market coverage, or whether the call can fail for unknown tickers.

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?

One short sentence, front-loaded with the resource and followed by a clarifying parenthetical; nothing is redundant. It is terse to the point of under-specification, but every word present earns its place.

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

Completeness3/5

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

For a simple one-parameter read tool with full annotation coverage this is roughly adequate, but with no output schema the agent still has no notion of the return shape (fields, units, nesting) beyond the three broad categories named. A brief note on what a result contains would close the gap.

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?

With a single parameter at 100% schema coverage (symbol documented as 'IDX ticker'), the schema carries the parameter burden. The description adds no meaning about symbol format or behavior beyond what the schema states, so the baseline of 3 applies.

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 names a specific resource ('key statistics for a company') and enumerates the categories returned (valuation, size, performance metrics), which lets an agent distinguish it from siblings like ratios or technicals. It never states a verb, but the read-only nature plus the parenthetical make the intent unambiguous.

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 how this differs from ratios, peer_comparison, or company_profile, and no stated scope such as single-company vs. comparative use. The agent must infer selection purely from the noun phrase.

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