Skip to main content
Glama

List unused images, models and audio

r3_assets_unused
Read-onlyIdempotent

The account's images, models and audio files that nothing uses — no project, no entity template, no other user's project — with each one's size and date, biggest first, and the total. The same report as the R3 app's Settings → Storage, by the same rules the deletes use. A model lists the images only it uses, an HDR / EXR image its preview image: they go with it. A texture set nothing uses is one item (kind textureSet) with its maps under it; a map of a set is never listed on its own. Blender (.blend) files are not part of it: they are the user's to keep or delete, listed by r3_blender_list. Pass kind to see one kind, limit for more rows (the totals always cover everything). It only reads; r3_asset_delete deletes an item by its kind and id (a plan, then a confirm), for what the user asked to remove. The scan can take several seconds.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOnly this kind: image, model, audio or textureSet.
limitNoHow many items to list (default 50, at most 200).

Output Schema

NameRequiredDescriptionDefault
itemsYes
shownYes
answerYesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance.
totalsYes
environmentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Only this kind: image, model or audio."New value: +"Only this kind: image, model, audio or textureSet."
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "image",
      -  "model",
      -  "audio"
      -]New value: +[
      +  "image",
      +  "model",
      +  "audio",
      +  "textureSet"
      +]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / answer
      Added value: +{
      +  "description": "This answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance.",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "items",
      -  "shown",
      -  "totals",
      -  "environment"
      -]New value: +[
      +  "items",
      +  "shown",
      +  "totals",
      +  "environment",
      +  "answer"
      +]
  3. First observed

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description corroborates with 'It only reads'. Beyond that it adds genuinely useful behavior: the scan can take several seconds, totals always cover everything regardless of `limit`, and the grouping rules (a model carries the images only it uses, an HDR/EXR image carries its preview, a texture set is one item with maps nested under it) match the rules the deletes use. That aggregation and grouping disclosure is real added value over the annotations, though it does not cover the response shape (which the output schema handles).

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?

Purpose and scope are front-loaded in the first sentence, and the remaining sentences each carry distinct information (grouping rules, exclusion of .blend, parameter behavior, read-only vs delete routing, latency). It runs long and the texture-set/model nesting sentences are dense, but nothing is redundant enough to cut without losing meaning.

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

Completeness5/5

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

For a zero-required-parameter read tool with an output schema, this covers everything an agent needs: what is included, what is excluded, how items are grouped, how parameters change output, what it does not do (delete), and expected latency. No material gap remains.

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

Parameters5/5

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

Schema coverage is 100%, so baseline would be 3; the description goes further by explaining the semantic consequence of `limit` — it expands rows but the totals always cover everything — which is not inferable from the schema's 'How many items to list'. It also frames `kind` as an optional narrowing of an otherwise complete report rather than a required scope.

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 states a specific resource scope ('The account's images, models and audio files that nothing uses') and enumerates the exclusion conditions — no project, no entity template, no other user's project — then adds the payload (size, date, sorted biggest first, plus totals). It also distinguishes itself from r3_image_list / r3_audio_list by defining 'unused' rather than just listing.

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?

Explicit routing is given: .blend files are handled by r3_blender_list, and removals go through r3_asset_delete with a kind and id using a plan-then-confirm flow. It also explains that `kind` narrows to one kind and `limit` extends rows, so the agent knows when to filter versus read the full report.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources