Skip to main content
Glama
Hermoso

Hermoso

Official

Save file(s) to OneDrive

save_to_onedrive

Save Hermoso render URLs or any uploaded file directly to a connected Microsoft OneDrive, choosing an optional folder and file name. Returns OneDrive files with a webViewLink for easy sharing.

Instructions

Save a Hermoso render — or ANY file — into the user’s connected Microsoft OneDrive. Pass a Hermoso render URL as url (or urls[] for several); for a local/external file, call upload_file first and pass the url it returns. Optional folder (created if new) + name. Returns the OneDrive file(s) with a webViewLink. Needs OneDrive connected (Connectors > OneDrive).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_to_onedrive"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoa single Hermoso render URL to save
nameNofile name (single save)
urlsNoseveral render URLs (up to 20) to save in one call
folderNoOneDrive folder name to save into (created if new)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.161

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare it is a non-destructive write to an open-world target, and the description adds real context on top: folders are created when new, the result includes a webViewLink, and up to 20 URLs can be batched. The main undisclosed behavior is idempotency — nothing says whether re-saving the same file overwrites or duplicates — despite idempotentHint=false.

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?

Front-loaded with the core action, then the input routing, then the prerequisite — a sensible order with almost no wasted wording. It is dense to the point of being a single run-on block, and the em-dash emphasis ('or ANY file') is slightly noisy, but every sentence carries usable information.

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 write tool with no output schema, the description covers the return value (files with a webViewLink), auth prerequisite, folder side effect, and batching limit. The one gap is that required parameters are empty, so the implicit rule that at least one of url or urls must be supplied is left unstated.

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 the schema already documents all four parameters, including the 20-URL cap and folder auto-creation. The description reinforces the url vs. urls[] choice but adds no syntax, format, or default-value detail beyond what the schema provides, so the 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?

States a specific verb and resource — saving a render or any file into the user's connected Microsoft OneDrive — and names the destination service explicitly, which separates it from the Google Drive siblings. It also scopes the accepted input types (render URL vs. local/external file), so an agent can tell what this tool handles 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 Guidelines5/5

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

Gives concrete routing instructions: pass a render URL as url, use urls[] for several, and call upload_file first for a local/external file and pass its returned url. It also states the prerequisite that OneDrive must be connected, which is exactly the condition an agent needs before attempting the call.

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

Deploy Server

Other Tools