Skip to main content
Glama
Sign In
VideoGenerationMCP

VideoGenerationMCP

by AvivK5498
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_asset

Retrieve the current state of an asset and refresh its TTL to maintain its availability.

Instructions

Get a single asset's current state (refreshes its TTL).

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": {
      "asset_id": "<asset_id>"
    },
    "name": "get_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 transparency burden. It explicitly discloses the non-obvious TTL refresh side effect, which is valuable beyond a plain read operation. However, it omits other traits like required permissions or error behavior, so it is not maximally transparent.

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 one concise sentence that efficiently communicates both the main purpose and a key side effect, with no redundant or filler 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?

For a simple, single-parameter tool, the description covers the core purpose and the significant TTL side effect. An output schema exists, so return details are handled. The lack of explicit alternatives or operational caveats makes it slightly incomplete, but it is largely adequate for the tool's simplicity.

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?

The schema has 0% description coverage for asset_id, and the description does not explain the parameter format or its relationship beyond the tool name. The phrase 'a single asset' indirectly ties asset_id to the asset, but this is insufficient to fully clarify the parameter's semantics.

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 uses the specific verb 'Get' plus the resource 'a single asset's current state', clearly distinguishing it from list_assets (which would retrieve multiple assets). The parenthetical about refreshing TTL adds further scope clarification.

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 description implies usage when a single asset's state is needed, and the TTL refresh hints at a reason to use it (extending asset life). However, it does not explicitly name alternatives or state when not to use it, leaving guidance at the implied level.

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