Skip to main content
Glama

media_inspect

Read-only

Inspect an asset to get duration, size, fps, audio details, and analysis status, plus an optional 4x3 contact sheet of evenly spaced frames.

Instructions

Probe an asset (duration, size, fps, audio, analyses done) and return a 4x3 contact sheet image of evenly spaced frames.

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": "media_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdYes
contactSheetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, and the description usefully adds the output nature: a 4x3 contact sheet of evenly spaced frames plus metadata fields. It does not disclose cost or latency (frame extraction can be slow), whether results are cached, or how the image is returned, which are the traits the annotations don't cover.

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 sentence, front-loaded with the action and followed by the concrete return shape. Nothing is padded and no clause is redundant.

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?

With no output schema, the description does well to describe the returned contact sheet and metadata, but it leaves the two parameters unexplained and says nothing about the cost or synchronicity of probing an asset. Adequate for a simple read tool, but not complete.

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 carries the full burden, yet it explains neither assetId nor contactSheet. Most notably, the contactSheet boolean that can suppress the image is never mentioned, so an agent would not know it can request metadata only.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("Probe an asset") and enumerates what the probe reports: duration, size, fps, audio, analyses done. That is far more specific than the bare name and reads differently from siblings like frames_get or analysis_get, though it never explicitly contrasts itself with them.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. An agent cannot tell from this text whether to call media_inspect, analysis_get, or frames_get to learn about an asset, so the routing decision is left entirely to inference.

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