Skip to main content
Glama

MotionSpec — web animation accessibility MCP

MotionSpec usage telemetry

motion_stats
Read-only

Operator telemetry of the hosted service (not your own usage); needs the operator key (header x-motionspec-key). This unauthenticated call returns access information only; it does not compile code, fetch URLs, run an audit or read usage data. Arguments are optional and unused. Returns isError:true with structuredContent {ok:false, error:'KEY_REQUIRED', tool, freeLocalAlternative} and text guidance. For your own local activity use 'npx -p motionspec motion stats' (MIT). It reads this machine's local activity, not hosted usage.

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_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the auth requirement (operator key header), the exact failure contract (isError:true with structuredContent {ok:false, error:'KEY_REQUIRED', tool, freeLocalAlternative} plus text guidance), and that it touches no code or network resources – consistent with openWorldHint:false. Minor deduction for the slightly confusing 'unauthenticated call' wording alongside the mandatory key.

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 identity and auth requirement, then the failure contract, then the local alternative – a sensible order with no filler. It loses a point for restating the 'not your own usage' distinction twice (the parenthetical and the closing sentence about local activity).

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?

Covers everything an agent needs for a zero-parameter, no-output-schema tool: auth, expected error payload, and the correct alternative for real usage data. The only gap is the tension between 'needs the operator key' and 'unauthenticated', which could leave the agent unsure whether the call will always fail without a key.

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?

With zero parameters the baseline is 4, and the description reinforces it by stating 'Arguments are optional and unused', so the agent knows nothing needs to be supplied. The empty schema already carries this; the sentence just confirms it.

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 resource and scope ('Operator telemetry of the hosted service, not your own usage') and explicitly excludes what it is not: it does not compile, fetch URLs, run an audit or read usage data. An agent can tell instantly how it differs from motion_compile, motion_audit and motion_validate.

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 the selection rule both ways: use this for hosted operator telemetry with the x-motionspec-key header, and use 'npx -p motionspec motion stats' for the caller's own local activity. The alternative and the condition that selects it are named explicitly.

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.