Skip to main content
Glama
Venice MCP Server

Venice MCP Server

Official
by veniceai

Venice Text Parser (PDF/DOCX/EPUB/PPTX/XLSX)

venice_text_parser

Extracts text from an HTTP(S) or base64 document URL by fetching and uploading it server-side, supporting wallet or API key authentication.

Instructions

Extract text from a document URL. Fetches the URL server-side and uploads the file as multipart/form-data. Supports x402 wallet auth (no Venice account needed) and API key.

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": {
      "url": "<url>"
    },
    "name": "venice_text_parser"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesDocument to parse: an http(s) URL or an inline base64 data URL. Include a concrete media type in data URLs, e.g. application/pdf or application/vnd.openxmlformats-officedocument.wordprocessingml.document for DOCX.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • addedInput schema / properties / url / description
      Added value: +"Document to parse: an http(s) URL or an inline base64 data URL. Include a concrete media type in data URLs, e.g. application/pdf or application/vnd.openxmlformats-officedocument.wordprocessingml.document for DOCX."
  2. First observedv0.2.0

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses genuinely useful behavior: the URL is fetched server-side, the file is uploaded as multipart/form-data, and both x402 wallet auth and API key auth are accepted. This is exactly the kind of operational context annotations cannot express. It stops short of 5 because it says nothing about size/page limits, failure modes, or cost implications, and readOnlyHint=false is left unexplained.

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?

Three short sentences, front-loaded with the core action, then behavior, then auth. Every sentence carries information with no filler. It is slightly under-terse in that supported formats live in the title rather than the description body.

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

Completeness3/5

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

For a one-parameter parser with no output schema, the definition should say roughly what comes back (raw text, per-page text, metadata) and restate supported formats inline. Auth modes and server-side fetching are covered, but return-shape expectations are left entirely to inference.

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 parameter's own description already spells out http(s) URLs vs. base64 data URLs with required media types. The description adds only the 'fetched server-side' nuance, which clarifies that no local upload step is needed but does not extend coverage of the single parameter.

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?

States a specific verb and resource: 'Extract text from a document URL.' The title adds the supported formats (PDF/DOCX/EPUB/PPTX/XLSX), so an agent knows this is a document-to-text tool rather than a general scraper. It does not explicitly distinguish itself from siblings like venice_web_scrape, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no mention of the obvious alternative (venice_web_scrape for HTML pages vs. this tool for binary documents). The only contextual hint is the auth note, which is about credentials, not tool selection.

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