Skip to main content
Glama

List scene templates

kreavo_list_scenes
Read-onlyIdempotent

List available scene templates. System templates (studio, lifestyle, outdoor, etc.) are available to all users. Custom scenes are your own extracted scenes. Params: filter? (all|system|custom, default all), category? (studio|lifestyle|outdoor|travel|fashion|seasonal|nightlife)

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

Input Schema

NameRequiredDescriptionDefault
filterNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 is fully covered. The description adds genuine scope context by explaining that system templates are shared across all users while custom scenes are the caller's own extracted scenes. It says nothing about result count, ordering, or pagination, which is the remaining behavioral gap.

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?

Front-loaded with the purpose, then scope semantics, then parameters — no filler sentences. The inline "Params: ..." formatting is compact and readable, though it is slightly listing-style rather than prose.

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-required-parameter read tool with no output schema, the definition covers purpose, filter semantics, and allowed values well. What keeps it from being complete is the absence of any note on how the two filters interact or what the listed results contain beyond template names.

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 0% and the schema declares both parameters as bare strings with no enum, so the description carries the full load — and it delivers by enumerating valid values for both (all|system|custom and the seven category values) plus the default of "all" for filter. The only omission is a default or behavior note for category when it is left out.

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?

"List available scene templates" states a specific verb (list) and a specific resource (scene templates), and the follow-up sentences define what a scene template is by contrasting system vs custom. It is clearly distinct from siblings like list_characters and list_models, though it never names them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the discovery step before scene-based generation, and the system/custom distinction hints at which filter to pick for which need. There is no explicit when-to-use or when-not-to-use statement and no alternative tool is named.

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