YuzuGrow

create_upload_url

Get a pre-signed URL to upload a file (avatar, demo video, music, etc). Creates an Asset record.

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": {
      "fileName": "<fileName>",
      "type": "<type>"
    },
    "name": "create_upload_url"
  }
}

Input Schema

Name	Required	Description
`type`	Yes	Asset type
`title`	No	Display title for the asset
`fileName`	Yes	Original file name with extension
`fileSize`	No	File size in bytes
`mimeType`	No	MIME type (auto-detected if omitted)
`productId`	No	Link to a product

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 30, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the call creates an Asset record, but it omits important behavioral details such as URL expiration, single-use constraints, required HTTP method, and authorization requirements.

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 two tight sentences with no waste. The primary action and its side effect are front-loaded and easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description gives the core purpose and side effect, but with no output schema and no annotations, it should say more about the returned URL and upload requirements. It remains minimally adequate because the input schema is fully documented.

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 all six parameters are already documented in the input schema. The description does not add parameter syntax, format, or usage details beyond the schema, so the baseline of 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 states a specific action: obtaining a pre-signed upload URL, with concrete examples and a disclosed side effect (creates an Asset record). An agent can distinguish this from sibling generation tools 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 Guidelines2/5

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

The description does not say when to use this tool versus alternatives, nor does it mention prerequisites such as authentication or required upload steps. Usage context is implied only by the phrase 'upload a file.'

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

All YuzuGrow tools Inspect

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

Need Help?