Skip to main content
Glama

Taiwan Monthly Revenue

taiwan_monthly_revenue
Read-onlyIdempotent

Monthly sales (月營收) reported by TWSE-listed companies: the month's revenue with month-on-month and year-on-year change, plus year-to-date totals. Taiwan mandates this disclosure by the 10th of the following month, so it is the earliest read on semiconductor and electronics demand anywhere. Pass a company for its own filing, or a sector to rank companies by revenue growth.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many companies to return when ranking, 1-100. Default 20.
symbolNoCompany code, English abbreviation or Chinese name. Omit to rank companies instead.
industryNoSector to rank within, e.g. "Semiconductor", "Shipping & Transportation". Omit for the whole market.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so safety is covered. The description adds genuinely useful context beyond annotations: the mandated 10th-of-month disclosure timing and the resulting recency ('earliest read on semiconductor and electronics demand'), which informs freshness expectations.

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?

Front-loads the resource and return metrics, then the timing context, then the two invocation modes. The 'earliest read on semiconductor demand' clause is slightly editorial but earns its place by conveying timeliness value.

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 describe the returned content (revenue, MoM, YoY, YTD). It covers the essential fields, though it omits details like pagination or ranking sort order.

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% with all three params documented, so the schema carries the burden. The description reinforces the symbol-vs-industry mutual-exclusion ranking behavior, but adds little syntax or format detail beyond what the schema already states.

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+resource (monthly sales 月營收 from TWSE-listed companies) and enumerates the returned metrics (MoM, YoY, YTD totals). This is clearly distinguishable from siblings like taiwan_stock_quote or taiwan_stock_valuation.

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?

Explicitly describes the two invocation modes: pass a company for its own filing, or a sector to rank companies by revenue growth. It gives clear context for use but doesn't name or exclude specific sibling alternatives, so it stops short of a 5.

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.