Skip to main content
Glama

Taipei Ledger

Monthly revenue

get_revenue
Read-onlyIdempotent

Monthly revenue history of one company (NT$, as filed with MOPS, from January 2021): revenue, year-on-year and month-on-month change per month, newest first, plus the latest month's measures (year to date, versus its own trend, how unusual, record month since, back to 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": {
      "company": "<company>"
    },
    "name": "get_revenue"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsNo
companyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the description's added value is the data provenance (as filed with MOPS, NT$), the historical start point (January 2021), result ordering (newest first), and the presence of derived latest-month measures. It does not disclose pagination, default window behavior, or error/empty-company behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, but the definition is one long sentence with a dense parenthetical and a trailing list of loosely named measures ('versus its own trend, how unusual, record month since, back to growth') that is harder to parse than a structured enumeration would be.

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?

With no output schema, the description usefully compensates by describing return contents, and it is complete about data scope. It remains incomplete on the two things an agent most needs to call it correctly: the 'months' window parameter and the acceptable company identifier format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning and it largely does not. 'One company' hints that 'company' is a single identifier but gives no format (ticker vs. name), and the 'months' parameter (default 24) is never mentioned at all.

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 concrete resource (monthly revenue history of ONE company) with unit (NT$), source (MOPS) and coverage window (from January 2021), then enumerates the returned fields. The 'one company' scope implicitly separates it from the sibling screen_revenue, though no alternative is named.

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?

Usage is only implied: an agent can infer this is the tool for per-company monthly revenue history, but the description contains no explicit when-to-use, when-not-to-use, or pointer to screen_revenue for multi-company screening.

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