Skip to main content
Glama
Sign In
Motion MCP Server

Motion MCP Server

by mattdkonig
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

motion_workspaces

List or retrieve Motion workspaces to manage your projects and schedules. Get workspace details by ID or view all available workspaces.

Instructions

Manage Motion workspaces - supports list and get operations

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": {
      "operation": "<operation>"
    },
    "name": "motion_workspaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationYesOperation to perform
workspaceIdNoWorkspace ID (required for get operation)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and only hints that operations are read-oriented ('list', 'get'). It does not disclose what happens during list vs get, permissions, or output structure.

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?

A single, front-loaded sentence with no redundant content. It efficiently states the resource and supported operations.

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

Completeness2/5

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

Given the tool has two parameters, no output schema, and no annotations, the description is too sparse. It lacks details about return values, required parameters for each operation, and potential errors.

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?

Schema coverage is 100%, so the baseline is 3. The description adds minimal value beyond schema, only noting that workspaceId is required for 'get', while 'operation' is simply described as 'Operation to perform'.

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 clearly identifies the resource (Motion workspaces) and explicitly lists supported operations ('list and get'). However, 'Manage' is a generic verb; the operation list provides the real clarity.

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

Usage Guidelines2/5

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

No guidance on when to use this tool compared to siblings like motion_projects or motion_tasks. It does not state required conditions or alternative tool suggestions.

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