Value Ledger 研值

top_growth

Read-onlyIdempotent

Taiwan-listed companies ranked by year-on-year monthly revenue growth, optionally within one industry, from official MOPS filings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "top_growth"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`month`	No	YYYY-MM；省略時使用最近已發布月份。未發布月份不推估。
`industry`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so safety needs no restating. The description adds real value by naming the data provenance (official MOPS filings) and implying descending rank order via 'top', but says nothing about ordering guarantees, ties, or what a result entry contains.

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 front-loaded sentence with no filler; the ranking criterion, the optional scope, and the source all appear before the period.

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 leaves the agent guessing at returned fields (company name? growth percentage? revenue figures?) and the sort direction. For a ranking tool with zero required params, that is a meaningful remaining gap beyond what annotations and schema cover.

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 only 33% — only month is documented (including the no-extrapolation rule). The description partially compensates by explaining industry as an optional scope filter and implying limit via 'top ... ranked', but the meaning of limit's default/cap and the industry matching semantics remain unstated.

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: companies 'ranked by year-on-year monthly revenue growth' from MOPS filings, plus the industry-narrowing option. This separates it reasonably well from get_company_revenue (single company), though it never names a sibling explicitly.

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 phrase 'optionally within one industry' hints at the scoped variant of use, implying broader ranking is the default. There is no explicit when-to-use/when-not or routing to compare_industry or get_company_revenue, leaving the agent to infer selection.

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

All Value Ledger 研值 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?