Skip to main content
Glama

render_options

Read-only

Lists the models, styles, qualities, cameras, and speeds accepted by render(), explaining what each option does so you can choose valid settings.

Instructions

The models, styles, qualities, cameras and speeds render() accepts, with what each one does.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds that each entry carries an explanation of what it does, but says nothing about return shape, size, or caching, which is the main practical concern for a catalogue lookup.

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?

One compact sentence with the enumerated categories front-loaded and no filler. It is a sentence fragment, which is fine for a definition, but a leading verb would have made the intent land faster.

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

Completeness4/5

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

For a zero-parameter, read-only lookup with no output schema, the description covers what categories come back and that each item is explained. Only the structure of the response (flat lists vs. nested per-category objects) is left unspecified, which is a minor gap.

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 no parameters, so schema coverage is moot and the baseline of 4 applies. The description correctly implies a parameterless static enumeration rather than suggesting any filtering arguments exist.

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 names the exact resource: the models, styles, qualities, cameras and speeds that render() accepts, plus per-item explanations. That distinguishes it from the render family (it is a lookup, not a render call), though it is a noun phrase with no explicit verb such as 'list' or 'returns'.

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?

Mentioning render() implies this is consulted before or alongside a render call, but the description never states when to use it, e.g. 'call before render to discover valid values,' nor does it rule out any alternative. Usage must be inferred.

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