Skip to main content
Glama
octoco-ltd

SheetsData MCP

by octoco-ltd
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

confirm_datasheet_upload

Destructive

Confirms a datasheet upload by verifying the file's integrity and validity, then creates document records and queues extraction after charging a fee.

Instructions

Confirm a datasheet upload started via request_datasheet_upload. Pass the upload_token you got back from the request step. The server downloads the uploaded bytes, re-hashes to verify integrity, validates that it's a real PDF with the MPN on the first page, creates the private Document + Component records, charges the upload fee (50¢), and queues extraction.

Success response: document_id, mpn, sha256, file_size_bytes, status='pending'. Poll check_extraction_status with the MPN to wait for extraction to finish (30s-2min typically).

Failure modes:

  • 'upload_not_found' — no bytes at the upload URL yet. Retry your curl upload.

  • 'sha256_mismatch' — uploaded bytes hash differs from expected_sha256. Re-compute the hash and re-request.

  • 'invalid_pdf' — bytes aren't a parseable PDF. No charge.

  • 'mpn_not_in_pdf' — MPN (or its stem) isn't on the first page. Either you uploaded the wrong file or it's a scanned image-only PDF. No charge.

  • 'token_expired' — upload token is older than 15 minutes. Restart via request_datasheet_upload.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
upload_tokenYesOpaque token returned by request_datasheet_upload.

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

Despite annotations indicating write operations (readOnlyHint=false, destructiveHint=true), the description adds detailed behavioral context: server downloads bytes, re-hashes, validates PDF, creates records, charges fee, queues extraction. It also explains failure modes and side effects like charges only on valid PDF.

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?

Description is well-structured with sections for main action, success response, and failure modes. It is somewhat lengthy but each sentence adds value; front-loads the core action.

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?

Without an output schema, the description provides the success response fields and directs to check_extraction_status. Covers all failure modes and side effects, making it complete for a complex tool with multiple outcomes.

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 covers 100% parameters with a description for upload_token. The description adds 'Pass the upload_token you got back from the request step', reinforcing the source but not adding new semantic value beyond the schema.

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?

The description clearly states 'Confirm a datasheet upload started via request_datasheet_upload', specifying the verb (confirm) and resource (datasheet upload). It distinguishes from siblings like request_datasheet_upload and check_extraction_status.

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?

Explicitly tells when to use: after request_datasheet_upload with the upload_token. Lists failure modes and how to handle each, providing clear context for when to retry or restart.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/octoco-ltd/sheetsdata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server