Skip to main content
Glama

inspect_dependencies

Report packed or missing assets and resolved paths for a Blender session, including explicit coverage limits.

Instructions

Report packed/missing assets and resolved paths. Reports coverage limits explicitly.

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": {
      "session_id": "<session_id>"
    },
    "name": "inspect_dependencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It discloses that coverage limits are reported explicitly, but it does not say whether the operation is read-only, how pagination behaves, what happens with an invalid session, or what the return structure looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is two short sentences with no filler, and the primary output is front-loaded. However, the second sentence is a fragment and the overall brevity leaves the definition under-specified for a three-parameter tool.

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?

With no annotations, no output schema, and 0% parameter description coverage, the definition is incomplete: it does not explain the required session_id, pagination behavior, or how to interpret packed/missing results. It gives only a high-level output summary and a note about coverage limits.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain session_id, limit, or offset at all. The phrase 'coverage limits' refers to report completeness, not the limit parameter, so it does not compensate for the undocumented parameters.

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 specific reporting action and names the artifacts it surfaces: packed/missing assets and resolved paths. This tells the agent it is a dependency/asset inspection tool, but it does not explicitly differentiate itself from sibling inspect_* tools or mention the session context, so it stops short of a 5.

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 guidance, no condition for choosing this over inspect_scene, inspect_object, or other inspection siblings, and no prerequisites such as needing a session_id. The note about coverage limits is not usage guidance.

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