Skip to main content
Glama

library

Read-onlyIdempotent

Look up style asset IDs by category or search term, with names and short notes, to get valid IDs for casting, acting, cameras, lights, places, and transitions.

Instructions

Read-only: the ids a style offers, by category (characters, objects, places, cameras, actions, emotions, text_presets, text_animations, transitions and outro moves, lights, looks, elements, samples), with names and short notes. With no category and no search it returns counts only; pass category and/or search to keep answers small. Every id you pass to cast, act, words, camera, light, place or transition must come from here. For ready-made shot recipes to add, use samples.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMost items per category (default 150).
styleNoA style id from list_styles. Default: the project's style.
searchNoWords to look for in id, name, group and note, like 'zoom' or 'sad'.
categoryNoOne of: characters, objects, places, cameras, actions, emotions, text_presets, text_animations, transitions, lights, looks, elements, samples.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • changedInput schema / properties / search / description
      Previous value: -"Words to look for, like 'zoom' or 'sad'."New value: +"Words to look for in id, name, group and note, like 'zoom' or 'sad'."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/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 safety is covered; the description adds genuinely new behavior: the response shape (ids with names and notes) and the degenerate case where no category and no search yields counts only. It stops short of mentioning pagination or default-limit implications beyond what the schema states, so it is strong but not exhaustive.

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?

Three sentences, front-loaded with the read-only nature and the core return semantics, and every sentence carries actionable information. The only waste is the inline category enumeration, which largely duplicates the schema's enum-style description for 'category'.

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 four-parameter, optional-argument listing tool with no output schema, the description covers return content, the empty-filter fallback, size-control advice, and the prerequisite relationship to consumer tools. An agent has everything needed to call it correctly on the first try.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by documenting cross-parameter interaction ('With no category and no search it returns counts only'), which the per-field schema descriptions do not convey. The 'category and/or search' phrasing also clarifies that the two act as combinable narrowing filters rather than alternatives.

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?

States a specific verb and resource ('the ids a style offers, by category') and enumerates the categories returned with their payload ('names and short notes'). It also distinguishes itself from the sibling 'samples' ('For ready-made shot recipes to add, use samples'), so an agent can tell the two apart without opening either schema.

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?

Gives explicit when-to-use ('Every id you pass to cast, act, words, camera, light, place or transition must come from here'), explicit alternative routing ('use samples' for shot recipes), and practical guidance on narrowing the call ('pass category and/or search to keep answers small'). Nothing about tool selection is left to inference.

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