Skip to main content
Glama

agentladle/financial-reports

by com.agentladle.mcp
OverviewDiscussionsAdmin

financialKeywordSearch

financialKeywordSearch
Destructive

Full-text keyword search across financial reports.

<critical_rules>

  1. NEVER input full sentences. Extract 1-5 core keywords.

  2. LANGUAGE ALIGNMENT — keywords MUST match the report language:

    • CN-A: Simplified Chinese (e.g. "净利润", "合并资产负债表")

    • HK: English (e.g. "net income", "consolidated balance sheet")

  3. COGNITIVE TRANSLATION: convert conversational wording into financial terminology.

  4. Report types (all markets): annual '{year}a4' (e.g. '2025a4'), interim '{year}h2' (e.g. '2026h2').

  5. Stock code format: CN-A 6 digits (000001), HK 5 digits (00700). Prefer stockCode and market returned by searchCompanyInfo. Do not invent padding.

  6. Cross-company search (no stockCode): reportType is REQUIRED.

  7. market is optional ('CN-A' | 'HK'). Omit to search all markets. </critical_rules>

Input Schema

NameRequiredDescriptionDefault
sizeNoNumber of fragments to return, default 5, max 1000
marketNoMarket: 'CN-A' | 'HK'. Optional. Omit to search all markets.
pageMaxNoMaximum page number (inclusive), optional
pageMinNoMinimum page number (inclusive), optional
keywordsYes1-5 keywords for full-text search
matchModeNoMatch mode: ANY (default) / ALL / MOST (at least 70%)
stockCodeNoStock code from searchCompanyInfo. CN-A: 6 digits; HK: 5 digits. Omit for cross-company search.
reportTypeNoReport type, e.g. 2025a4 (annual), 2026h2 (interim). Required when stockCode is omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / market / description
      Previous value: -"Market: 'CN-A' | 'HK' | 'US'. Optional. Omit to search all markets."New value: +"Market: 'CN-A' | 'HK'. Optional. Omit to search all markets."
    • changedInput schema / properties / stockCode / description
      Previous value: -"Stock code from searchCompanyInfo. CN-A: 6 digits; HK: 5 digits; US: uppercase ticker. Omit for cross-company search."New value: +"Stock code from searchCompanyInfo. CN-A: 6 digits; HK: 5 digits. Omit for cross-company search."
  2. Changed8 schema fields changed
    • changedInput schema / properties / keywords / description
      Previous value: -"关键词列表(1-5个),用于全文检索"New value: +"1-5 keywords for full-text search"
    • addedInput schema / properties / market
      Added value: +{
+  "description": "Market: 'CN-A' | 'HK' | 'US'. Optional. Omit to search all markets.",
+  "type": "string"
+}
    • changedInput schema / properties / matchMode / description
      Previous value: -"匹配模式:'ANY'(任一,默认)/'ALL'(全部)/'MOST'(至少70%)"New value: +"Match mode: ANY (default) / ALL / MOST (at least 70%)"
    • changedInput schema / properties / pageMax / description
      Previous value: -"最大页码(含),仅返回页码<=此值的结果,可选"New value: +"Maximum page number (inclusive), optional"
    • changedInput schema / properties / pageMin / description
      Previous value: -"最小页码(含),仅返回页码>=此值的结果,可选"New value: +"Minimum page number (inclusive), optional"
    • changedInput schema / properties / reportType / description
      Previous value: -"报告类型标识符(当前已支持如:2023a4,2024a4,2025a4),可选,不指定则检索所有报告"New value: +"Report type, e.g. 2025a4 (annual), 2026h2 (interim). Required when stockCode is omitted."
    • changedInput schema / properties / size / description
      Previous value: -"返回片段数量,默认5,最大1000"New value: +"Number of fragments to return, default 5, max 1000"
    • changedInput schema / properties / stockCode / description
      Previous value: -"股票代码,如'000001',可选,不指定则全市场检索"New value: +"Stock code from searchCompanyInfo. CN-A: 6 digits; HK: 5 digits; US: uppercase ticker. Omit for cross-company search."
  3. First observed

TDQS

A4.1/5.0
Behavior1/5

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

Annotation Contradiction: the description presents the tool as a pure read/search operation ('Full-text keyword search', 'read that page'), while annotations declare destructiveHint=true. The description never clarifies whether the search can modify or delete data, so the agent receives conflicting safety signals.

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?

The description is longer than average, but it is densely structured with an explicit strategy and critical rules. Every section prevents a specific invocation error, and the core purpose is front-loaded before the tactical guidance.

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?

The description covers all invocation-critical behavior: when to use it, prerequisites, language rules, code formats, and required parameters. The main gap is the lack of an output schema and only indirect mention of the return shape ('returned page number'), leaving fragment contents and matching results somewhat underspecified.

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

Parameters5/5

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

Even though the schema covers all parameters, the description adds decisive constraints: 1-5 keywords only, no full sentences, language alignment (Simplified Chinese for CN-A, English for HK), reportType formats like '2025a4'/'2026h2', stock code digit rules, and reportType required for cross-company searches. This materially improves correct invocation.

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?

The description opens with a specific action and resource — 'Full-text keyword search across financial reports' — and then sharpens the boundary by referencing sibling tools. It clearly distinguishes this tool from getFinancialReportPages and searchCompanyInfo, so an agent can tell it apart without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The strategy section is an explicit decision tree: use this tool for specific facts or locating sections, skip it for TOC or known page numbers, and call searchCompanyInfo first when the company is unknown. It names the alternatives and the exact conditions that route to them.

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

All agentladle/financial-reports toolsInspect
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