Skip to main content
Glama

Check a PDF upload

get_pdf_upload_status
Read-onlyIdempotent

Check whether a single-use PDF upload is ready to pass to prepare_fax.

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": {
      "upload_id": "<upload_id>"
    },
    "name": "get_pdf_upload_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
upload_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare this is a read-only, idempotent, non-destructive check, so the safety burden is lifted; the description's real contribution is the 'single-use' property, warning that the upload cannot be reused. It says nothing about what readiness states exist or what the response contains, which matters because there is no output schema.

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?

One sentence with zero filler, and the operative condition ('ready to pass to prepare_fax') is front-loaded rather than buried.

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 simple read-only check the description covers purpose and pipeline position, but with no output schema the agent is left guessing what a readiness result looks like and how to interpret a not-ready answer. Adding the possible outcomes and the source of upload_id would close the remaining gap.

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?

Only one parameter, upload_id, and schema coverage is 0%, so the description is the only place its meaning could be explained. It implies upload_id identifies a single-use PDF upload but does not say where the ID comes from (presumably create_pdf_upload) or any format detail beyond the schema's uuid.

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 verb and resource ('Check whether a single-use PDF upload is ready') and ties it to the concrete next step ('to pass to prepare_fax'), which cleanly separates it from create_pdf_upload and get_fax_status among the siblings.

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

Usage Guidelines4/5

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

Implies the workflow position clearly: call this before prepare_fax to confirm the upload is ready, which tells an agent both when to use it and what it gates. It does not explicitly say what to do while not ready (poll again, wait, fail), so it stops short of full when/when-not guidance.

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