Skip to main content
Glama

Value Ledger 研值

get_company_revenue

Read-onlyIdempotent

查已發布公司 JSON 的月營收、月增、年增與累計。金額為千元新台幣;缺漏欄位為 null,不從其他月份補值。

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_company_revenue"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
monthNoYYYY-MM;省略時使用最近已發布月份。未發布月份不推估。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful semantics beyond that: amounts are in thousands of NTD, missing fields are null, and values are never backfilled from other months — a real anti-assumption guard for an agent.

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?

Two tight sentences: the first states what is returned, the second states the unit convention and the null/no-backfill rule. Nothing is wasted and the payload description is front-loaded.

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 the work of naming the returned fields and units, which is the key gap it needed to fill, and the null/no-backfill rule prevents misreading missing data as zero. It still says nothing about response shape or whether the result covers one company versus several, which is the only remaining 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?

Schema coverage is 50%: the month parameter is well documented in the schema itself (YYYY-MM, defaults to latest published, no extrapolation), while code carries only a pattern. The description adds nothing about either parameter, but the schema plus the pattern makes the required code self-evident, so baseline 3 is right.

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 verb (查) and resource (公司 JSON 的月營收) and enumerates the returned metrics (月增、年增、累計), so the agent knows exactly what data comes back. It does not differentiate itself from siblings such as get_monthly_revenue_history or compare_industry, which leaves some ambiguity about which to pick.

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: the tool fetches published revenue for a company code, with an optional month defaulting to the latest published month. There is no explicit when-to-use or when-not-to-use guidance and no mention of the sibling tools that cover history or comparisons.

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