Skip to main content
Glama

agentladle/financial-reports

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 by market (approx. last 3 years; pick {year} from the user request, do not invent older years):

    • CN-A: annual '{year}a4', interim '{year}h2', Q1 '{year}q1', Q3 '{year}q3'.

    • HK: annual '{year}a4', interim '{year}h2' only (no quarterly).

  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>

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": {
      "keywords": "<keywords>"
    },
    "name": "financialKeywordSearch"
  }
}

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. CN-A: {year}a4|{year}h2|{year}q1|{year}q3; HK: {year}a4|{year}h2. Required when stockCode is omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / reportType / description
      Previous value: -"Report type, e.g. 2025a4 (annual), 2026h2 (interim). Required when stockCode is omitted."New value: +"Report type. CN-A: {year}a4|{year}h2|{year}q1|{year}q3; HK: {year}a4|{year}h2. Required when stockCode is omitted."
  2. 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."
  3. 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."
  4. First observed

TDQS

A4.3/5.0
Behavior3/5

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

The description adds genuine behavioral constraints the annotations don't carry: the CN-A/HK data-availability boundary, the rule that cross-company search requires reportType, and per-market report-type availability (HK has no quarterly). However, it says nothing about what a result actually looks like (fragments vs. pages), latency, or result caps, and the annotations are unusually aggressive for a search tool (readOnlyHint=false, destructiveHint=true), with the description doing nothing to reconcile that.

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?

Front-loaded purpose sentence, then tagged <strategy> and <critical_rules> sections, with the fastest-path decision table first. Dense but every rule is actionable; the numbered lists are slightly padded (rule 6/7 restate the schema) but nothing is seriously wasteful.

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?

For an 8-parameter tool with no output schema, the definition covers the full workflow: keyword formatting, market/language selection, code formats, report-type availability, and the hand-off to getFinancialReportPages. The only real gap is the shape of the response (fragment count, what 'size' returns in practice), which is implied but never stated.

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 coverage is 100%, so the baseline is 3, but the description goes further: it constrains keywords to 1-5, mandates language alignment per market (Simplified Chinese for CN-A, English for HK), instructs cognitive translation of conversational wording into financial terminology, and shows reportType patterns in context of 'approx. last 3 years'. That is real added meaning beyond the schema's terse enum-style hints.

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?

States a specific verb and resource ('Full-text keyword search across financial reports') and immediately distinguishes itself from getFinancialReportPages ('KNOWN PAGE NUMBER: skip this tool') and searchCompanyInfo ('Unknown company name/code: call searchCompanyInfo first'). An agent can tell which tool to reach for without opening any 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> block gives four explicit routing rules including two when-NOT-to-use conditions with the exact alternative call to make instead (TOC lookup, known page number). It also states the prerequisite path for resolving an unknown company (searchCompanyInfo, market required) and the data-scope boundary ('Currently CN-A and HK have data').

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