Skip to main content
Glama

Verify file uploads

verify_file_picker_uploads
Read-onlyIdempotent

Verify that the selected workspace’s temporary uploads are complete and unexpired before returning them to the agent. Verification does not create or change a brand or add files to a Brand Library. Returns each upload_id with verified true, or verified false and a reason.

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": {
      "workspace_id": "<workspace_id>",
      "upload_ids": "<upload_ids>"
    },
    "name": "verify_file_picker_uploads"
  }
}

Input Schema

NameRequiredDescriptionDefault
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
upload_idsYesUpload IDs returned by create_file_picker_uploads.
workspace_idYesDestination selected when opening the file picker. Pass that workspace's ID, or null when the picker targets the personal workspace.

Output Schema

NameRequiredDescriptionDefault
filesYesOne result for each requested upload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description adds useful context on top: no brand is created or changed and no files enter a Brand Library. It also discloses the per-item result contract (verified true, or false with a reason), though it doesn't say whether unexpired-but-missing uploads are reported differently.

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 tight sentences, front-loaded with the core action and followed by scope exclusions and result shape. The final sentence mildly overlaps the output schema, but nothing is padded or ambiguous.

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 three-parameter read-only verification tool with full schema coverage, rich annotations, and an output schema, the description covers purpose, non-effects, and the shape of results. An agent has everything needed to decide to call it and interpret the response.

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%, so workspace_id, upload_ids, and the analytics-only llm_model are already fully documented in the schema. The description implies the workspace scoping and per-upload_id results but adds no syntax, limits (e.g., max 30 IDs), or null-workspace semantics beyond the schema, 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?

The description names a specific verb (verify) and resource (the selected workspace's temporary uploads), narrows the check to completeness and expiration, and explicitly distinguishes the operation from brand mutation or library additions, which separates it from siblings like create_file_picker_uploads and add_to_library.

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?

It gives clear context for use: verify uploads 'before returning them to the agent,' which implicitly places it after upload creation. It also states what the tool does not do, but it never names a concrete alternative or failure-handling path (e.g., what to do when verified is false).

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