Skip to main content
Glama

Motion Fab Library

Get a technique

get_technique
Read-only

One technique with its code: code.html, code.css and code.js make one standalone composition (CDN libraries and Google Fonts only), plus everything search_techniques gives. Adapt it to your piece rather than pasting it whole.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_technique"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAn id from search_techniques.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnly and openWorld=false; the description adds meaningful return-shape detail beyond that — three named code fields forming one standalone composition restricted to CDN libraries and Google Fonts. With no output schema, this disclosure does real work, though it doesn't cover size/truncation or error behavior for a bad id.

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?

Two sentences, front-loaded with what is returned and followed by the composition constraint and usage hint. No filler, though the parenthetical and clause stacking make it slightly denser than necessary.

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 one-parameter read tool with no output schema, the description sufficiently characterizes the returned object and its constraints. Missing only edge-case details such as invalid-id behavior.

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

Parameters3/5

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

There is a single required id parameter and schema coverage is 100%, which already documents it as an id from search_techniques. The description adds no meaning about the parameter beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource — fetch one technique together with its code.html, code.css and code.js composition. It also distinguishes itself from search_techniques by saying it returns everything that tool gives plus the code payload.

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?

The id is implied to come from search_techniques (schema echoes this), and 'adapt it to your piece rather than pasting it whole' gives guidance on how to consume the result. There is no explicit when-not-to-use or contrast with get_recipe, so guidance is implied rather than stated.

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