Skip to main content
Glama

三域医研 · 科研算法引擎 (SanYu Research Engine)

Tumour growth inhibition (TGI) / 抑瘤率 TGI

tumor_growth_inhibition
Read-only

Tumour growth inhibition (TGI) / 抑瘤率 TGI | USE WHEN: compute TGI (%) from control vs treated tumour volumes, with a group comparison | ALIASES: 抑瘤率, TGI, 肿瘤抑制率, tumour growth inhibition, 抑瘤实验, 药效评价 | RETURNS: TGI 与统计检验

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": {
      "ctrl_volumes": "<ctrl_volumes>",
      "treat_volumes": "<treat_volumes>"
    },
    "name": "tumor_growth_inhibition"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctrl_volumesYes对照组体积
treat_volumesYes给药组体积

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, non-destructive and closed-world, so the safety profile is covered. The description adds that the tool also performs a group comparison and returns statistical testing, which is useful behavioral context beyond the annotations, but it does not say which test or how results are shaped.

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 pipe-delimited line with the purpose first, then usage, aliases, and return summary — front-loaded and scannable. The long bilingual alias list earns its place for query matching but is the bulkiest element.

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 two-parameter calculation tool with full schema coverage, the definition covers purpose, inputs, and a rough return note. With no output schema, the vague 'returns TGI and statistical testing' leaves the agent unable to anticipate output fields or which test is applied.

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 both parameters (control-group volumes, treated-group volumes) are already documented in the schema. The description only restates that mapping; it adds no detail on units, whether array entries are per-animal measurements, or minimum sample sizes, which the schema leaves ambiguous.

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 states a specific verb and output ('compute TGI (%)') on a specific resource ('control vs treated tumour volumes'), so an agent can tell this apart from a summary/plotting tool like tumor_volume_curve. It does not name that sibling explicitly, so differentiation is inferred rather than stated.

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?

The 'USE WHEN' clause gives a clear triggering condition: compute TGI from control vs treated volumes with a group comparison. No when-not conditions or named alternatives are given, so the agent must infer boundaries against tumor_volume_curve or stats_toolbox.

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.