Skip to main content
Glama

SinoAILab AI & Robotics

Extract Empirical Data Tables (SinoAILab)

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.6/5.0
Behavior3/5

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

The annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the source-format constraint (V2.1 Markdown or V1 HTML dossier) and the output format (clean Markdown tables), but it does not explain missing-dossier behavior, error handling, or other operational limits.

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?

The definition is two sentences with the core operation front-loaded and no redundant wording. The second sentence efficiently adds use-case context without diluting the main purpose.

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 simple, read-only tool with one fully documented parameter and no output schema, the description covers the source dossier formats and the returned Markdown table format. The main remaining gap is that it does not state the prerequisite relationship with get_paper_dossier or how to handle a missing dossier.

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?

There is only one parameter, and schema coverage is 100%, with the schema already documenting that identifier accepts a paper slug, DOI, or numeric ID. The description does not add any further meaning about the identifier or its format, so the baseline of 3 is appropriate.

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 gives a specific verb and resource: 'Extract normalized empirical data tables' from a paper's dossier into Markdown. That makes the operation clear, but it does not explicitly distinguish this tool from sibling get_paper_dossier or state whether that sibling is a prerequisite source.

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 names example use cases such as benchmarking metrics, materials properties, clinical outcomes, and experimental comparisons. This implies when the tool is useful, but there is no explicit when-to-use versus alternatives, no exclusion conditions, and no stated prerequisite that a dossier must already exist.

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