Skip to main content
Glama
Sign In
motionspec

motionspec

by MasterPlayspots
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

MotionSpec catalog & authoring rules

motion_catalog
Read-only

Retrieve verified motion primitives and MotionSpec authoring rules so you can write, validate, and compile a spec correctly.

Instructions

Returns the catalog of verified motion primitives (names, purpose, parameter schemas, defaults) plus the authoring rules for writing a MotionSpec. Call this FIRST, then write the spec yourself, check it with motion_validate and compile it with motion_compile. Free motion check: https://motionspec.dev/motion-check · paid Motion Report (9 USD, one-time): https://motionspec.dev/pricing?src=mcp-motion_catalog#p-report.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context: this is a discovery/priming tool that must precede authoring, and it returns structured reference data rather than performing any operation. It doesn't discuss size of the catalog or pagination, which would have completed the picture.

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

Conciseness3/5

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

The tool-relevant content is front-loaded and efficient: one sentence of purpose, one sentence of workflow. However, the trailing 'Free motion check' URL and 'paid Motion Report (9 USD)' pricing link are promotional rather than functional, adding noise an agent must filter when deciding whether to call the tool.

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?

With no output schema and no parameters, the description carries the burden of describing return content, and it does so by naming the catalog fields. Combined with the explicit sequencing into motion_validate and motion_compile, an agent has enough to call this correctly. The only omission is any sense of catalog size or response format.

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, so the baseline is 4. The description does earn some credit by describing what the (absent) output schema would otherwise document — the returned catalog fields — helping the agent anticipate the result shape.

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?

States a specific verb and resource ('Returns the catalog of verified motion primitives') and enumerates exactly what's inside (names, purpose, parameter schemas, defaults), plus the authoring rules for writing a MotionSpec. This is clearly distinguishable from siblings like motion_validate or motion_compile, which act on a spec rather than supply the vocabulary for authoring one.

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

Usage Guidelines5/5

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

Gives an explicit ordered workflow: 'Call this FIRST, then write the spec yourself, check it with motion_validate and compile it with motion_compile.' It names both alternative tools and the precise step at which each applies, leaving no inference needed about sequencing.

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

Deploy Server

Other Tools