Skip to main content
Glama

get_company_detail

按 company_id 取公司详情 + 关联计数:管线药品数、BD 交易数、投融资事件数。某个计数超时会在 count_errors 里点名,不会静默当 0。

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": {
      "company_id": "<company_id>"
    },
    "name": "get_company_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_idYessearch_companies 返回的 id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries real weight here and delivers a non-obvious behavioral trait: partial-failure semantics where a timed-out count is surfaced in count_errors instead of being silently reported as 0. That is exactly the kind of context an agent cannot infer from schema. It still omits latency/cost expectations and confirmation that no mutation occurs.

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?

Two short clauses, zero filler, with the primary action front-loaded and the caveat about count_errors placed after the returns. Nothing could be cut without losing information.

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 a one-parameter read tool with no output schema, the description covers what is returned (detail plus three counts) and the failure mode. It does not say what fields the 'detail' itself contains, but the core calling information is present.

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?

Only one parameter, and the schema already documents it at 100% coverage with the same 'search_companies 返回的 id' provenance. The description adds no syntax or format detail beyond the schema, 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 a specific verb and resource ('按 company_id 取公司详情') and enumerates the payload (pipeline drug count, BD deal count, financing event count), which clearly distinguishes it from the search_* siblings that only return ids. No sibling is named explicitly, so it stops short of a 5.

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 'company_id = id returned by search_companies' hint implies the workflow (search first, then fetch detail), but the description never states when to use this tool versus the search tools or any prerequisites. Usage is implied rather than stated.

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.