Skip to main content
Glama
Sign In

Novence

by ai.novence
OverviewDiscussionsAdmin

Get upload URLs (batch)

get_upload_urls_batch

Presign many site files at once (max 100). Prefer this over get_upload_url for multi-file sites. After PUTs, call confirm_uploads_batch, not confirm_upload.

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": {
      "project_id": "<project_id>",
      "files": "<files>"
    },
    "name": "get_upload_urls_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesFiles to presign, max 100. Each needs a site-relative path.
project_idYesHosting project UUID from create_project or list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / files / description
      Added value: +"Files to presign, max 100. Each needs a site-relative path."
    • addedInput schema / properties / files / items / properties / content_type / description
      Added value: +"MIME type for the file. Optional; inferred from the path extension when omitted."
    • addedInput schema / properties / files / items / properties / path / description
      Added value: +"Site-relative path (e.g. index.html or css/app.css). No leading slash required."
    • addedInput schema / properties / project_id / description
      Added value: +"Hosting project UUID from create_project or list_projects."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only mark the operation as not read-only and not destructive, so the description adds meaningful workflow context: the 100-file cap, the presign-then-PUT-then-confirm sequence, and the batch-specific confirmation step. It does not mention URL expiration or permission requirements, but the core behavior is well disclosed.

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?

Three short, information-dense sentences. Each sentence earns its place: the first states the operation and limit, the second gives selection guidance, and the third specifies the required follow-up. No filler or repetition.

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 two-parameter tool with no output schema, the description covers the main behavior, the batching limit, the preferred alternative, and the required next step. It does not explicitly describe the response format, but 'Presign' plus 'Get upload URLs' in the title makes the return value clear enough.

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%, and both project_id and files are already documented. The description adds only the 'max 100' constraint and workflow-level guidance, which is helpful but does not substantially deepen understanding of the individual parameters beyond the schema.

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 uses a specific verb ('Presign') and resource ('site files') and distinguishes this batch variant from the single-file get_upload_url. The max-100 limit and explicit naming of the sibling tool make the tool's purpose unambiguous.

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?

The description explicitly says 'Prefer this over get_upload_url for multi-file sites' and specifies the correct follow-up: 'After PUTs, call confirm_uploads_batch, not confirm_upload.' This gives clear when-to-use and when-not-to-use guidance.

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

All Novence 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