Skip to main content
Glama

Value Ledger 研值

get_monthly_revenue_history

Read-onlyIdempotent

Monthly revenue history of a Taiwan-listed company from official MOPS filings, with MoM and YoY growth.

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": {
      "code": "<code>"
    },
    "name": "get_monthly_revenue_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
monthsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful provenance ('official MOPS filings') and discloses the derived growth metrics, but says nothing about currency/units, data lag, or coverage gaps.

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?

A single compact sentence, front-loaded with the resource and back-loaded with the value-add metrics. Every clause carries information; nothing is wasted.

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?

With no output schema, the description does its job by naming the payload (monthly revenue series plus MoM and YoY growth). Only the units/currency of the revenue figures and the bounded range of months (max 60) are 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 description coverage is 0%, so the schema documents neither parameter. The description partially compensates: 'Taiwan-listed company' implies code is a local ticker, and 'history'/'monthly' implies months is a lookback window, but the numeric code pattern and the default of 24 are left unexplained.

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?

States a specific verb-resource pair: monthly revenue history for a Taiwan-listed company, with the source (official MOPS filings) and the derived metrics (MoM and YoY growth). It does not distinguish itself from the sibling get_company_revenue, which sounds like it covers overlapping ground.

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 words 'history' and the 'months' parameter imply a time-series use case, so the intended usage is inferable. There is no explicit guidance on when to use this instead of get_company_revenue or compare_industry, and no prerequisites are named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources