Skip to main content
Glama

SinoGreenTech Clean Energy

Extract Empirical Data Tables (SinoGreenTech)

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

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

Annotations already state readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the source versions (V2.1 Markdown / V1 HTML) and that output is 'normalized' Markdown. It does not say what happens when a paper has no empirical tables or when the dossier is missing/other version, which would matter for agent retry logic.

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, with the use-case sentence second. Minor filler ('directly', 'clean', 'Useful for') keeps it from being maximally tight, but nothing is wasted or buried.

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 input source, transformation, and output format, which is close to sufficient. The gaps are edge-case behavior (empty results, version mismatch, invalid identifier) rather than core invocation information.

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 does the work. The description only implies the identifier refers to a paper via 'a paper's ... dossier', adding no new format or constraint detail, 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?

The description gives a specific verb and resource ('Extract normalized empirical data tables') plus the exact source ('a paper's V2.1 Markdown or V1 HTML dossier') and output form ('clean Markdown tables'). That is enough to distinguish it from get_paper_dossier (which fetches the dossier itself) and search_research, though it never names an alternative explicitly.

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 offers use cases (benchmarking metrics, materials properties, clinical outcomes, experimental comparisons), which implies when the tool is appropriate. However, there are no exclusions, no prerequisites (e.g., dossier must exist first), and no guidance on when to prefer this over pulling the full dossier.

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