Skip to main content
Glama

studio_library

Retrieve the versioned canonical character registry and reference hashes without provider credentials, so agents can reuse consistent character identities across audiovisual projects.

Instructions

Show reusable, versioned canonical character registry and reference hashes without provider credentials.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden; it does add real value by stating the tool works "without provider credentials," which tells the agent no auth or setup is required. However it never confirms read-only semantics, whether output is cached/versioned snapshots, pagination, or side effects — modest gaps for a zero-parameter tool, but still undisclosed.

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?

A single front-loaded sentence with the verb first and no filler or redundancy — efficient. It loses a point only because the compressed noun stack makes the sentence harder to parse than a two-clause phrasing would be.

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?

For a zero-parameter tool with no output schema, the description must carry the full burden of explaining what comes back, and "registry and reference hashes" only gestures at the shape of the response. It is enough to recognize the tool as a read of canonical character data, but not enough to predict the returned structure or how "versioned" entries relate.

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?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate; a baseline of 4 applies. The mention of "versioned" and "reference hashes" describes output content rather than inputs, which is harmless but does not change the parameter picture.

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

Purpose3/5

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

"Show" plus a compound resource phrase ("reusable, versioned canonical character registry and reference hashes") conveys a read of some canonical character catalog, but the noun stack is dense and ambiguous — an agent cannot tell whether the result is a list, a lookup table, or a hash manifest. It also does not distinguish its role from siblings such as studio_discover_upstream or studio_status.

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 explicit when-to-use statement, no excluded cases, and no named alternative among the many studio_* siblings. The only usable cue is the trailing clause "without provider credentials," which implies a condition (unauthenticated/local access) but never states when an agent should reach for this tool instead of another.

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