Skip to main content
Glama

3DAssets.dev

Finalize upload

finalize_upload

After PUTting the file to the URL from get_upload_url, describe the asset and submit it for processing and review.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNo
titleYes
aiModelNoContributor-reported model ID or custom model/tool name; use list_ai_models for suggestions. Omit if unknown.
licenseNoFixed CC0 1.0 Universal dedication; no licence selectioncc0-1.0
summaryYesPlain 1–2 sentence description
categoryYesFrom list_categories
sourceUrlNoWhere the original was first published
previewKeyNo
aiGeneratedNoAI helped create geometry, code or textures; not merely uploading
attestationYesRequired contributor acceptance (including for agent submissions): I confirm that I created this asset or hold the rights to publish it under CC0 1.0 Universal, and agree to dedicate it to the public domain under CC0 so anyone can use, modify and redistribute it for personal or commercial purposes without attribution. I understand this dedication is irrevocable and the asset will be reviewed before publishing.
descriptionNoMarkdown: scale, pivot, what is included
quarantineKeyYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The description states that the tool submits the asset for processing and review, disclosing the primary side effect. It does not mention idempotency or failure modes, but for a submission action this level of transparency is reasonable.

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?

The description is a single, concise sentence that conveys the essential action and context without extraneous detail. It is well-structured and easy to parse.

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?

The description fits the two-step upload flow and references get_upload_url, giving appropriate context. It does not describe the post-submission process or response format, but this is acceptable for a finalize/submit tool and the schema covers required fields.

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?

The schema covers 67% of parameters with descriptions, but some parameters (quarantineKey, previewKey, tags) lack explanations. The tool description adds little beyond referencing the upload flow, so agents may not understand the origin or purpose of these fields.

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 clearly states the tool's role: after PUTting a file to a URL from get_upload_url, it describes the asset and submits it for processing/review. It effectively distinguishes this finalization step from the initial upload step.

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 description gives a clear sequential condition ('After PUTting the file to the URL from get_upload_url'), implying when to use it. It does not explicitly compare with alternatives like submit_asset_from_url, but the sequential context is sufficient for most agents.

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.