IT桔子 MCP

search_events

按时间、行业、标签、轮次等条件分页查询事件。event_type 表示物理来源：invse 融资/轮次事件、merger 并购事件；event_category 表示业务分类：investment 投资轮次、listing 上市相关、merger 并购；也可直接使用 ipo、上市、并购等常见词面，服务端会自动归一化；支持 event_ids 精确/批量查询已知事件，并可用 has_fa=true 只返回已披露 FA 的事件；is_underwater 可筛选未披露水下事件，尝鲜版和标准版不可查看水下事件明细。

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

Input Schema

Name	Required	Description	Default
`cities`	No
`cursor`	No
`fields`	No
`has_fa`	No
`tag_ids`	No
`date_end`	No
`location`	No
`event_ids`	No
`page_size`	No
`provinces`	No
`round_ids`	No
`scope_ids`	No
`date_start`	No
`event_type`	No
`is_underwater`	No
`sub_scope_ids`	No
`event_category`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 13, 2026

addedInput schema / properties / event_ids

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "integer"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Event Ids"
+}

addedInput schema / properties / has_fa

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Has Fa"
+}

Changed1 schema field changedJul 8, 2026

addedInput schema / properties / is_underwater

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Is Underwater"
+}

First observedJul 7, 2026

TDQS

B3.4/5.0

Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden, and it does substantial work. It discloses that the server normalizes free-text synonyms such as ipo, 上市, and 并购 into canonical values, and that 尝鲜版 and 标准版 tiers cannot view underwater event details. It does not explain pagination limits or default page size.

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 one dense but well-ordered sentence cluster: filters first, then parameter semantics, then access caveats. Each clause about normalization and tier restrictions earns its place, though the clause about common words could be folded into the event_category explanation.

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?

An output schema exists, so return values need not be explained. For a 17-parameter tool with no schema descriptions, however, the description leaves many filter parameters and the pagination contract unaddressed, which is a meaningful gap.

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

Parameters2/5

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

Schema coverage is 0% across 17 parameters, so the description must compensate, and it only partly does. It gives real meaning to event_type, event_category, event_ids, has_fa, and is_underwater, but leaves scope_ids, sub_scope_ids, fields, cities, provinces, location, cursor, and page_size undefined.

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 resource: a paginated query of events filtered by time, industry, tags, and round. It also explains the distinction between event_type as a physical source and event_category as a business classification. It stops short of naming a sibling such as get_company_funding_events or search_companies, so the agent gets the purpose but not the boundary against siblings.

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 description explains when to use specific parameters: use event_ids for exact or batch lookup, use has_fa to restrict results to disclosed FA events, and use is_underwater for undisclosed events. These notes imply usage but do not explicitly say when to choose this tool over the other event and company search tools.

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

All IT桔子 MCP 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.