Skip to main content
Glama
Sign In
Mobile Design MCP

Mobile Design MCP

by noxpublishing
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

analyze_transition

Extract time-indexed review frames from a local video interval to inspect transition timing and visual states without inferring original easing, springs, or haptics.

Instructions

Extract time-indexed review frames from a local video interval. Does not infer original easing, springs or haptics.

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": {
      "recordingId": "<recordingId>",
      "startMs": "<startMs>",
      "endMs": "<endMs>"
    },
    "name": "analyze_transition"
  }
}

Input Schema

NameRequiredDescriptionDefault
endMsYes
framesNo
startMsYes
recordingIdYes
inlineFramesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, non-idempotent, non-destructive; the description doesn't disclose what side effects or artifacts (e.g., written frame files) make it non-read-only, leaving that gap. It does add real value by ruling out inferred easing/springs/haptics, which no structured field conveys.

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 short sentences with the primary action front-loaded and the limitation immediately after; nothing is wasted, though the second sentence could be framed as an explicit scope condition rather than a bare negation.

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 five-parameter extraction tool with no output schema and no annotation detail, the definition is missing parameter explanations (frame count, inline frames) and any hint of what is returned, so it is not fully complete despite being adequate on purpose and scope.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, but it only loosely implies the video interval (recordingId/startMs/endMs). The 'frames' count (3-12, default 6) and 'inlineFrames' flag are not explained anywhere, leaving two of five parameters semantically opaque.

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?

Names a specific verb ('Extract') and resource ('time-indexed review frames') scoped to a 'local video interval', which is more precise than the vague sibling names like analyze-style tools. It doesn't explicitly contrast with build_design_review_packet or import_recording, so it falls short of the top score.

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?

The description states what the tool does not do ('Does not infer original easing, springs or haptics'), which is a useful scope boundary, but it gives no guidance on when to call it versus alternatives such as build_design_review_packet or import_recording, nor any prerequisites.

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