Skip to main content
Glama
Sign In

Spacery

by io.github.lukehollis
OverviewDiscussionsAdmin

Finish upload

finish_upload

Checks that every uploaded file is complete and submits the space for processing. The account is emailed when the space is ready.

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": {
      "space_id": "<space_id>"
    },
    "name": "finish_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional notes for processing, such as what the capture is or how the tour should go.
outputNoWhat to build: "splat", a 3DGS (3D Gaussian splat) visitors move through freely (the default for photos, video and 360 captures); "tour", a guided tour of 360 panoramas (the default for E57 scans); or "auto" to use those defaults. Set it only when the person asks for one.
submitNoDefaults to true.
space_idYesThe space ID (12 hexadecimal characters) from create_space or space_status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, and idempotent=false. The description adds genuinely new behavioral context beyond those: it performs a completeness check, kicks off asynchronous processing, and emails the account when the space is ready. The non-idempotent trait is not called out, which is a minor gap.

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 tight sentences, both front-loaded with the core action and outcome. No filler or repetition of schema or annotation content.

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?

With no output schema, the description usefully explains the asynchronous outcome via the email notification. It leaves open what happens if files are incomplete, what the immediate response is, and how re-invocation behaves given the non-idempotent annotation, but covers the essential flow.

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%, so the schema already documents space_id, notes, output, and submit in detail (including enum semantics). The description adds no parameter-level information at all, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it checks uploaded files for completeness and submits the space for processing. This clearly positions it as the finalization step in the upload pipeline, distinct from upload_files and space_status. It stops short of explicitly naming siblings, but the purpose is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied by the pipeline position (after upload_files, before wait_for_tour). The description never states when to call it versus alternatives, nor any prerequisites such as needing all files uploaded first. Adequate context but no explicit 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.

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