Skip to main content
Glama

search_person_investment_cases

按人物ID或人物姓名分页查询人物投资案例,可按被投公司标签、行业和轮次筛选,适合回答某位投资人个人参与投资过哪些公司;高权限套餐可查看未披露水下事件标识。

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_person_investment_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
fieldsNo
page_sizeNo
person_idNo
round_idsNo
scope_idsNo
is_underwaterNo
sub_scope_idsNo
person_keywordNo
company_tag_idsNo
company_tag_match_modeNounion

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / additionalProperties
      Added value: +true
    • removedOutput schema / properties
      Removed value: -{
      -  "result": {
      -    "additionalProperties": true,
      -    "title": "Result",
      -    "type": "object"
      -  }
      -}
    • removedOutput schema / required
      Removed value: -[
      -  "result"
      -]
    • changedOutput schema / title
      Previous value: -"search_person_investment_cases_toolOutput"New value: +"search_person_investment_cases_toolDictOutput"
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose two useful traits beyond the schema: results are paginated, and the underwater/disclosed-status marker is gated by a high-privilege plan. It does not say whether at least one of person_id/person_keyword must be supplied, what happens if both are omitted, or how defaults behave.

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?

A single dense sentence that front-loads the primary keys and filters before the use case. No filler, though the clause structure is long enough that the filtering and permission clauses blur together slightly.

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?

The presence of an output schema removes the need to describe return values, and the permission note is a good addition. For an 11-parameter tool with zero schema documentation, however, the description still leaves too many parameters and the identifier-requirement rule unexplained.

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 0% across 11 parameters, so the description must compensate. It maps the main ones (person_id/person_keyword, company_tag_ids, industry scopes, round_ids, is_underwater), but leaves cursor, fields, page_size, scope_ids vs sub_scope_ids, and especially company_tag_match_mode (union/intersection) without any stated meaning.

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 states a specific verb and resource ('分页查询人物投资案例') along with the lookup keys (person ID or person name) and the exact question it answers ('某位投资人个人参与投资过哪些公司'). The word '个人' distinguishes it from company- and investor-level case searches without needing to enumerate siblings.

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

Usage Guidelines4/5

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

It gives a clear when-to-use condition: answering which companies a specific investor personally invested in. It does not name an alternative (e.g., search_company_investment_cases or search_investor_cases) or state when to prefer those, so routing between the three case-search tools is left to 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.