Skip to main content
Glama

get_remotion_cinematic_patterns

Read-only

Fetch the 69 premium cinematic and motion graphics patterns (Blur-to-Sharp, CSS 3D, Aurora backgrounds, etc.) to use when writing Remotion React code.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 the safety profile is known. The description adds useful content detail (count and categories of patterns) but does not describe the return format, whether all patterns are returned at once, or any pagination behavior.

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

Conciseness5/5

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

The definition is a single sentence, front-loaded with the main action and resource, followed by examples and usage context. Every phrase contributes useful information without repetition or filler.

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 simple, parameterless catalog-fetch tool with rich safety annotations, the description covers what is fetched and when to use it. The main minor gap is that it does not specify the return shape or whether the full set is delivered in one response, but given the tool's simplicity this is a small omission.

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 has zero parameters, so there is no parameter semantics to clarify. The baseline for a parameterless tool is 4, and the description does not need to add anything beyond the empty schema.

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?

The description uses a specific verb ('Fetch') and a clearly scoped resource ('the 69 premium cinematic and motion graphics patterns'), reinforced with concrete examples (Blur-to-Sharp, CSS 3D, Aurora backgrounds). It also states the intended use context ('when writing Remotion React code'), which distinguishes it from the sibling tools focused on plugins and media uploads.

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

Usage Guidelines4/5

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

The phrase 'to use when writing Remotion React code' gives a clear use context, so an agent can tell when this tool is applicable. It does not explicitly name alternatives or exclusions, but the sibling tools are unrelated, and no obvious similar retrieval tool exists among them.

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