Skip to main content
Glama
Sign In
SheetsData MCP

SheetsData MCP

by octoco-ltd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Check Datasheet Status

check_extraction_status
Read-onlyIdempotent

Check extraction progress for up to 20 electronic component parts, returning status, timing estimates, errors, and related ready parts to guide polling or reading.

Instructions

Free. Extraction status of 1-20 parts. A part being read reports current_step, elapsed_seconds, estimated_remaining_seconds with a range, and poll_after_seconds; a failed one reports its error; a part that isn't ready may list related_ready part numbers whose datasheet is readable now. A datasheet nobody has read before usually takes 1-3 minutes, 5 or more for a large one or a busy queue. These are estimates, not deadlines. A part whose PDF is still being looked for reads 'resolving'. Not final. Keep polling while the status is 'resolving', 'queued', 'pending' or 'extracting' (after poll_after_seconds); stop at 'ready', 'failed', 'no_source' or 'unsupported'. datasheet_status: 'ready' → read it; 'extracting' / 'queued' / 'pending' / 'resolving' → poll check_extraction_status; 'not_extracted' → prefetch_datasheets; 'no_source' / 'unsupported' → request_datasheet_upload. Full list in the server instructions.

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": {
      "part_numbers": "<part_numbers>"
    },
    "name": "check_extraction_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
part_numbersYes1-20 parts. Specific manufacturer part number (MPN) or LCSC number (e.g. 'TPS54302DDCR', 'C2837938'). Not a value ('100nF'), description or reference designator ('R1').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.0
    • changedInput schema / properties / part_numbers / description
      Previous value: -"1-20 MPNs to check. Must be specific manufacturer part numbers, not values or descriptions."New value: +"1-20 parts. Specific manufacturer part number (MPN) or LCSC number (e.g. 'TPS54302DDCR', 'C2837938'). Not a value ('100nF'), description or reference designator ('R1')."
  2. Changed1 schema field changedv1.3.2
    • changedInput schema / properties / part_numbers / description
      Previous value: -"List of MPNs to check (max 20)"New value: +"1-20 MPNs to check. Must be specific manufacturer part numbers, not values or descriptions."
  3. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover safety (readOnly, idempotent, non-destructive), and the description adds substantial behavioral context beyond them: it is free to call, expected latency is 1-3 minutes (5+ for large files or busy queues), timings are estimates not deadlines, and 'resolving' means the PDF is still being located. It also enumerates the fields returned per part state.

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?

Front-loaded with the most important fact ('Free', scope of 1-20 parts), and nearly every sentence carries operational value. The middle section is dense and semi-colon heavy, which slightly reduces scanability but not substance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden and does so: it describes per-state return fields (current_step, elapsed_seconds, estimated_remaining_seconds, poll_after_seconds, error, related_ready). Combined with the polling and routing rules, an agent has everything needed to call and interpret it.

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 schema already documents the MPN/LCSC format and the 'not a value/designator' constraint. The description only restates the 1-20 bound, adding no format or syntax detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (datasheet extraction status) for a bounded set of 1-20 parts, with the verb 'check' implied by the name. It distinguishes itself from siblings by explicitly mapping status values to the tools to use next (read_datasheet, prefetch_datasheets, request_datasheet_upload).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-poll rules: keep polling on 'resolving', 'queued', 'pending', 'extracting' (after poll_after_seconds); stop at 'ready', 'failed', 'no_source', 'unsupported'. It also routes each terminal status to the correct alternative tool, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools