Skip to main content
Glama
zenith-sb-mcp

zenith-sb-mcp

ratios

Read-only

Fetch key financial metrics for a company by IDX ticker to compare profitability, leverage, and valuation from Stockbit market data.

Instructions

Financial ratios for a company.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesIDX ticker

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 known. The description adds nothing beyond that: no indication of which ratio set is returned, whether values are trailing or forward, what currency/units apply, or any caveats about the open-world data source.

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?

A single short sentence with no padding and the key noun front-loaded. It is efficiently structured, though efficiency here edges toward under-specification rather than crispness.

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?

With no output schema and a one-parameter tool, the description is the only place to explain what ratio categories come back and in what units. As written it leaves an agent unable to predict the response content at all.

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?

Only one parameter exists and the schema documents it at 100% coverage with 'IDX ticker', so the schema carries the load. 'For a company' vaguely reinforces that symbol identifies an issuer but adds no format or exchange nuance beyond the schema.

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?

The phrase 'Financial ratios for a company' names a resource but gives no verb and no scope detail, so an agent cannot tell which ratios, for which period, or how this differs from siblings like keystats or peer_comparison that also surface financial metrics.

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 guidance on when to pick this over keystats, peer_comparison, or technicals, and no prerequisites or exclusions are stated. The agent must infer selection from names alone.

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