Skip to main content
Glama

docs_tools_pdf_metadata

[$x402 pago por llamada] Lee los metadatos de un PDF (título, autor, páginas, etc.) vía pdfinfo. Solo lectura, no modifica el archivo.

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": {
      "file_base64": "<file_base64>"
    },
    "name": "docs_tools_pdf_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.
file_base64YesContenido del archivo codificado en base64 (o data URL). Se convierte a multipart/form-data internamente.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description must carry the behavioral burden and it does partially: it states 'Solo lectura, no modifica el archivo' and flags the x402 per-call payment model, which is non-obvious context. It omits what happens on malformed/non-PDF input, and does not describe the shape of the returned metadata beyond a partial field list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence plus a bracketed pricing tag, front-loading the payment model and then the action. Every clause carries information; nothing is redundant.

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?

No output schema exists, so the description must convey the return value, and it does so with representative fields (título, autor, páginas, etc.) plus the read-only guarantee and the payment requirement. Only the failure behavior for invalid PDFs is left unaddressed, which is a minor gap for a simple read tool.

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 description coverage is 100%, so both file_base64 and x_payment are already documented in the schema, making 3 the baseline. The bracketed x402 note in the description corroborates the payment parameter but adds no new syntax or constraint beyond what the schema states.

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 ('Lee los metadatos de un PDF') and enumerates the returned fields (título, autor, páginas), plus names the underlying mechanism (`pdfinfo`). It does not explicitly distinguish itself from nearby siblings like img_tools_metadata or web_tools_metadata, so an agent must infer the format split from the input type.

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?

Usage is implied by 'Lee los metadatos de un PDF' – an agent knows to call it when it wants PDF metadata. There is no explicit when-not guidance or mention of alternatives such as docs_tools_ocr or docs_tools_to_markdown for content extraction rather than metadata.

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