Skip to main content
Glama

SinoAgriTech Crop & AgriTech

Extract Empirical Data Tables (SinoAgriTech)

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 already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description still adds real content: it says the output is normalized, arrives as clean Markdown rather than raw V1 HTML or V2.1 Markdown, and that the source is a paper dossier. It omits failure behavior, e.g. what comes back when a paper has no empirical tables or an identifier cannot be resolved.

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 with the action verb front-loaded and no redundant phrasing; the format qualifiers (V2.1 Markdown, V1 HTML) are compactly embedded. The second sentence is a generic use-case list that borders on filling rather than earning its space, so it is not quite exemplary.

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?

One required parameter, read-only, no output schema, so the description carries the return-shape burden and does so by naming clean Markdown tables and their normalized nature. Missing only edge-case behavior for empty or unresolvable identifiers, which keeps it short of a 5.

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 coverage is 100% and the sole parameter is documented as "Paper slug, DOI, or numeric ID." The description only reinforces that the identifier points at a paper and its dossier, adding no syntax, format preference, or resolution-order detail beyond the schema. 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?

Specific verb plus resource: "Extract normalized empirical data tables ... into clean Markdown tables." It also pins the source format (a paper's V2.1 Markdown or V1 HTML dossier), which is more than the name conveys. It does not name any sibling, so the agent must infer the relationship to get_paper_dossier on its own.

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 cases (benchmarking metrics, materials properties, clinical outcomes, experimental comparisons), which is scenario context but not selection guidance. It never states when to prefer this over get_paper_dossier or search_research, nor any precondition such as requiring that a dossier already exist. Usage is implied rather than stated.

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