Skip to main content
Glama
Sign In

Prubex

by com.prubex
OverviewDiscussionsAdmin

Check an upload

attachments_check_upload_status
Read-onlyIdempotent

Says whether the files on an upload link are in. Use it after attachments_generate_upload_link, once you or the user have uploaded: pending (not every file is in yet, so no tokens: if you uploaded them yourself, POST finish_url; if the user says they are done, ask them to check the page), expired, or completed with an upload_token per file for mail_send, mail_reply, mail_forward or mail_create_draft. Uploaded files are deleted after 24 hours. Example: { "upload_id": "upl_…" }.

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": "attachments_check_upload_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
upload_idYesThe upload id (`upl_…`) from the upload link.

Output Schema

NameRequiredDescriptionDefault
filesYes
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: the three possible statuses, that `pending` returns no tokens, the operational step to take in each case, which downstream tools consume the tokens, and the 24-hour deletion window for uploaded files.

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?

Purpose is front-loaded in the first sentence and every sentence carries operational content, but the middle sentence is a dense run-on with nested parentheticals that is harder to parse than it needs to be.

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?

For a single-parameter polling tool with an output schema present, the description covers everything an agent needs: prerequisite tool, status meanings, follow-up actions, token consumption path, and retention policy. Nothing material is missing.

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 schema property already documents upload_id as the `upl_…` id from the upload link. The description's trailing example repeats that format rather than adding new meaning, so baseline 3 applies.

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 ('Says whether the files on an upload link are in') and ties it to a named sibling, attachments_generate_upload_link, so an agent can distinguish it from the link-generation tool without opening the schema.

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 says when to call it (after attachments_generate_upload_link, once uploading has happened) and gives branching guidance per outcome: on `pending`, POST `finish_url` if you uploaded yourself or ask the user to check the page; `expired`; `completed` yields tokens for the mail tools. Alternatives and next actions are named, not implied.

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

All Prubex toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources