Skip to main content
Glama

SinoBioData Biomedical Research

Extract Empirical Data Tables (SinoBioData)

extract_empirical_tables
Read-only

Extract normalized empirical data tables directly from a paper's V2.1 Markdown or V1 HTML dossier into clean Markdown tables. Useful for benchmarking metrics, materials properties, clinical outcomes, or experimental comparisons.

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": {
      "identifier": "<identifier>"
    },
    "name": "extract_empirical_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYesPaper slug, DOI, or numeric 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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safe-read behavior is covered. Beyond that, the description discloses a real behavioral dependency: extraction targets a specific dossier version (V2.1 Markdown or V1 HTML), implying results vary by dossier availability, and it states the return shape (Markdown tables). It omits failure behavior, table-count limits, and whether 'normalized' entails post-processing.

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 sentences with no filler, and the core action plus source is front-loaded ahead of the use-case sentence. Every clause carries information an agent can act on.

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-only extraction tool with no output schema, the description covers the source, the transformation, and the output medium. It is slightly short on what a returned 'table set' looks like (one table vs. many, naming conventions) and on behavior when no empirical tables exist, but nothing critical to invoking it correctly is missing.

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% and the single identifier parameter already documents accepted forms (paper slug, DOI, numeric ID). The description only reinforces that the identifier refers to a paper; it adds no syntax examples, precedence between ID forms, or error semantics. Baseline 3 applies since the schema does the work.

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 names a specific verb and resource ('Extract normalized empirical data tables') and pins the source ('a paper's V2.1 Markdown or V1 HTML dossier') plus the output form ('clean Markdown tables'). That makes it distinguishable from a dossier-fetch tool like get_paper_dossier, but no sibling or alternative is named explicitly, so it stops short of full differentiation.

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 second sentence lists motivating use cases (benchmarking metrics, materials properties, clinical outcomes, experimental comparisons), which implies when the tool is valuable. It gives no explicit when-not guidance, no prerequisites (e.g., whether a dossier must exist first, or which dossier version is preferred), and no pointer to alternatives.

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.

Resources