Skip to main content
Glama

SinoTechIntel Materials & Tech

Extract Empirical Data Tables (SinoTechIntel)

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

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

Annotations only declare readOnlyHint and openWorldHint, so the description's disclosure that the tool reads specifically V2.1 Markdown or V1 HTML dossiers and returns clean Markdown tables adds real behavioral context the annotations do not carry. It still omits failure behavior (missing dossier, no tables found) and any output-size limits, keeping it short of a 5.

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?

Two sentences, front-loaded with the core action and source constraint. The 'Useful for…' list is slightly expendable and the 'SinoTechIntel' branding in the title adds nothing, but there is no redundant or confusing wording.

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 single-parameter read-only extraction tool with annotations and no output schema, the definition covers source location, output format, and typical use cases. The main remaining gap is what happens when a paper has no extractable tables or the dossier version is unavailable.

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?

With a single parameter at 100% schema description coverage ('Paper slug, DOI, or numeric ID'), the schema already fully documents the input. The description adds no extra guidance on identifier format or resolution, so the baseline 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?

The description uses a specific verb+resource pair: extract normalized empirical data tables from a paper's dossier into clean Markdown tables. The source is also scoped ('V2.1 Markdown or V1 HTML dossier'), which distinguishes it from a generic paper-fetching sibling, though it never explicitly contrasts itself with get_paper_dossier.

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 gives use-case flavor ('benchmarking metrics, materials properties, clinical outcomes, or experimental comparisons'), which implies when the tool is relevant, but it never states when to prefer this over get_paper_dossier or when not to call it (e.g., papers without empirical tables). Usage is implied rather than prescribed.

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