Skip to main content
Glama

Create a secure PDF upload

create_pdf_upload

Create a single-use 15-minute URL for handing a PDF to Edwyna. Uploading does not prepare, charge, or send a 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": {
      "filename": "<filename>"
    },
    "name": "create_pdf_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYesPDF filename.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, non-idempotent write with openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior the annotations cannot: the URL is single-use and expires in 15 minutes, and the call has no prepare/charge/send side effects. It does not say what happens on expiry or whether a new call is required to retry.

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?

Two short clauses, front-loaded with the action and the 15-minute single-use constraint, with zero filler. Every sentence carries information an agent needs.

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?

For a one-parameter tool with no output schema, the description conveys the essentials: what is produced (a URL), its lifetime and single-use nature, and what it does not do. The only gap is post-upload flow—how the returned URL is consumed or what happens after expiry.

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 exists and schema coverage is 100%, so the schema already documents filename (max 180 chars). The description adds only marginal meaning, implying the accepted file type is PDF; baseline 3 applies when the schema does the heavy lifting.

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: create a single-use 15-minute upload URL for a PDF. It also carves out scope by saying the upload does not prepare, charge, or send a fax, which separates it from siblings like prepare_fax and send_fax without naming them.

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?

The clause 'Uploading does not prepare, charge, or send a fax' gives an explicit when-not boundary and implies the follow-up steps route to prepare_fax/send_fax. It stops short of naming those alternatives or stating the positive precondition (e.g. call this before preparing a fax), so guidance is clear but not fully explicit.

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