Skip to main content
Glama

Taipei Ledger

Revenue screen

screen_revenue
Read-onlyIdempotent

Screen every company on the latest month of revenue. Filters: industry (e.g. 'Semiconductors', 'Computers & peripherals'), board ('TWSE' or 'TPEx'), year-on-year growth range as fractions (min_yoy=0.5 means at least +50%), minimum monthly revenue in NT$, record months only, companies back to growth only. sort_by one of yoy, mom, ytd_yoy, vs_trend, unusual_z, revenue.

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": "screen_revenue"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardNo
limitNo
max_yoyNo
min_yoyNo
sort_byNoyoy
industryNo
descendingNo
records_onlyNo
min_revenue_ntdNo
back_to_growth_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds real behavioral substance beyond that: yoy is expressed as fractions, min_yoy=0.5 means +50%, revenue is in NT$, and results are confined to the latest month. It doesn't state the return shape or what `limit` does to results, which keeps it below 5.

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?

The purpose is front-loaded in the first clause, and the filter/sort inventory follows without filler. The block is dense and slightly run-on, but every sentence carries operative information an agent needs to build a query.

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?

For a 10-parameter screening tool with zero schema descriptions and no output schema, the description covers filtering and sorting semantics well but says nothing about the result shape or how `limit` bounds the output. An agent can call it correctly, but cannot predict what it gets back.

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

Parameters4/5

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

Schema description coverage is 0% across 10 parameters with no enums, so the description carries the full burden — and it does well for most: board values ('TWSE'/'TPEx'), industry examples, fraction semantics for yoy, NT$ units for min revenue, and the valid sort_by keys. It leaves `limit`, `descending`, and `max_yoy` unaddressed, but the growth-range phrasing covers max_yoy by implication.

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 opens with a specific verb and scope: 'Screen every company on the latest month of revenue.' That distinguishes it in practice from the single-company `get_revenue` sibling. It stops short of naming an alternative explicitly, so it is clear but not fully sibling-differentiated.

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 implied by the screening/sorting filters — an agent can infer it is for broad, filtered lists rather than one company. There is no explicit when-not guidance and no named alternative (e.g. pointing to `get_revenue` for a single company), so selection still requires inference.

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