Skip to main content
Glama
Sign In
Mobile Design MCP

Mobile Design MCP

by noxpublishing
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

import_recording

Import a local screenshot or video into your reference library, hashing it and retaining platform/version provenance.

Instructions

Copy a local screenshot/video into your owned reference library, hash it and retain platform/version provenance.

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": {
      "path": "<path>",
      "title": "<title>",
      "platform": "<platform>"
    },
    "name": "import_recording"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
tagsNo
appIdNo
titleYes
platformYes
osVersionNo
appVersionNo
capturedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false and openWorld=false, so the safety profile is covered structurally. The description usefully adds that the source is copied rather than moved (original stays intact) and that hashing plus provenance capture occur, but says nothing about duplicate handling, deduplication behavior, or the copy destination. That is a modest contribution on top of the annotations.

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?

One compact sentence with the action and the outcome front-loaded, and no wasted clauses. It is under-specified rather than bloated, which is a different problem captured in the other dimensions.

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?

A write tool with 8 parameters, zero schema descriptions, and no output schema needs the description to explain inputs and the resulting record. Instead it gives only a one-line summary, so an agent lacks enough information to fill required fields like platform, title, or path correctly.

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% across 8 parameters, so the description carries the entire burden and mostly fails to. Only a loose mapping exists: 'platform/version provenance' gestures at the platform, osVersion and appVersion fields, while path, title, tags, appId, and capturedAt are given no meaning anywhere.

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?

Uses a specific verb ('Copy') with a concrete resource ('local screenshot/video into your owned reference library') and names the side effects (hash, provenance retention). However, it does not distinguish this from the sibling 'import_app', leaving the agent to guess which import path applies to a given file.

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?

There is no guidance on when to use this versus 'import_app', no statement of supported file types or size limits, and no prerequisites such as the path needing to be locally readable by the server. The 'owned reference library' phrasing hints at scope but provides no exclusions.

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