Skip to main content
Glama

inspect_media_assets

Read-onlyIdempotent

Inventory local image, font, video, and audio assets and report byte sizes to audit project media and storage use.

Instructions

Inventory local image, font, video and audio assets and byte sizes.

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": {
      "project": "<project>"
    },
    "name": "inspect_media_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description contributes only the scoping word "local" and the fact that byte sizes are reported; it says nothing about recursion depth, ignore rules, symlink handling, or cost on large asset trees.

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?

A single front-loaded sentence with no filler or redundancy. Nothing is padded, and the resource list is enumerated compactly.

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

Completeness2/5

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

An output schema exists, so return values need not be described. However, for a tool whose sole required input is an undocumented "project" string, the definition leaves an agent unable to tell what value to supply or how the inventory is scoped - a real gap for otherwise simple tools.

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?

There is one required parameter, "project", with zero schema description coverage, and the description never mentions it or explains how a project scopes the asset scan. With low coverage the description is expected to compensate, and it does not.

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 states a concrete verb ("Inventory") plus a specific resource set (local image, font, video and audio assets) and notes that byte sizes are included. It reads clearly against the inspect_* siblings, though it never names an alternative tool or otherwise differentiates itself from them explicitly.

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 among the many sibling analysis tools. The only implicit signal is the word "local", which hints at on-disk scope, but nothing tells the agent under what circumstances this inventory step should be chosen over, say, inspect_render or inspect_audio_levels.

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