Skip to main content
Glama
Sign In

CutClip.one

by one.cutclip
OverviewDiscussionsAdmin

asset.get

Fetch one asset's metadata (type, source, mime type, duration/dimensions if known) plus a downloadUrl for its file: a plain HTTP GET, no auth header needed, valid 24h (call again for a fresh one)

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": {
      "assetId": "<assetId>"
    },
    "name": "asset.get"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations the description carries the full load, and it delivers real behavioral facts: the downloadUrl is a plain HTTP GET needing no auth header, expires after 24h, and can be refreshed by re-calling. It omits error behavior for an unknown assetId and whether missing metadata fields are null or absent (only 'if known').

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?

One front-loaded sentence whose clauses each add information: return fields, URL mechanics, auth, expiry, refresh. No redundancy.

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 one-parameter read tool with no output schema, the description covers return contents, URL auth and lifetime, and refresh behavior. The remaining gap is assetId semantics and error handling, which matters somewhat given 0% schema coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain the single assetId parameter, and it does not — no format, provenance, or accepted ID shape. The only hint is the phrase 'one asset's', which adds nothing beyond the parameter name.

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 (fetch) and resource (one asset) and enumerates what comes back (type, source, mime type, duration/dimensions, downloadUrl). An agent can tell this apart from asset.list or asset.upload without opening any schema.

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?

The single-asset framing implies this is the tool for a known assetId rather than browsing, which indirectly routes against asset.list. But no sibling is named and no when-not condition is stated; usage is inferred rather than explicit.

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

All CutClip.one 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