ReportGem Global Research

search_meetings

Search global and China earnings-call transcripts and meeting notes, distinguishing body-text evidence from listing-only hits. 检索全球和中国会议纪要、业绩会记录，区分正文证据与清单命中。

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": {
      "query": "<query>"
    },
    "name": "search_meetings"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of meeting records to return (1-20)
`query`	Yes	Company, ticker, institution, industry or meeting keyword
`region`	No	global = earnings calls and meetings of global listed companies; china = China company meeting notes and investor-relations records; all = both	all
`date_to`	No	Latest publication date to include, ISO format YYYY-MM-DD; omit for no upper bound
`date_from`	No	Earliest publication date to include, ISO format YYYY-MM-DD; omit for no lower bound
`output_language`	No	Preferred language of returned titles and excerpts: en = English, zh = Chinese	en

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 7, 2026

addedInput schema / properties / date_from / description

Added value: +"Earliest publication date to include, ISO format YYYY-MM-DD; omit for no lower bound"

addedInput schema / properties / date_to / description

Added value: +"Latest publication date to include, ISO format YYYY-MM-DD; omit for no upper bound"

addedInput schema / properties / limit / description

Added value: +"Maximum number of meeting records to return (1-20)"

addedInput schema / properties / output_language / description

Added value: +"Preferred language of returned titles and excerpts: en = English, zh = Chinese"

addedInput schema / properties / region / description

Added value: +"global = earnings calls and meetings of global listed companies; china = China company meeting notes and investor-relations records; all = both"

First observedOct 20, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The annotations already declare non-read-only, non-idempotent, and non-destructive behavior, and the description adds useful result semantics by noting that body-text evidence is distinguished from listing-only hits. However, it does not clarify the surprising non-read-only side effect or explain permissions, rate limits, or other operational behavior.

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 description is two compact sentences with the purpose and result-classification front-loaded. The bilingual repetition is acceptable but adds some length without new information.

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 six-parameter search tool with an output schema, the description covers the corpus and one important result distinction but omits filter scope, selection guidance, and side-effect context. The output schema reduces the need to explain return shape, but routing guidance remains thin.

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 description coverage is 100%, so the input schema already documents query, region, date filters, limit, and output language. The description adds no parameter-level meaning beyond what the schema provides, so the baseline of 3 applies.

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 the specific verb 'Search' and the resource 'global and China earnings-call transcripts and meeting notes,' plus a result distinction between body-text evidence and listing-only hits. The domain is clear, though it does not explicitly differentiate itself from sibling tools such as search_filings or search_research.

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

Usage Guidelines2/5

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

Provides no explicit when-to-use or when-not-to-use guidance relative to search_filings, search_research, search_visuals, or get_evidence. Usage is only implied by the meeting/transcript resource, leaving the agent to infer routing.

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

All ReportGem Global Research 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?