Skip to main content
Glama
Sign In
Mobile Design MCP

Mobile Design MCP

by noxpublishing
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

mobbin_call

Read-only

Invoke a discovered, read-only official Mobbin MCP tool to access mobile design references without saving retrieved content locally.

Instructions

Call a discovered, explicitly read-only official Mobbin MCP tool without persisting its content locally.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
argumentsNo

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 already declare readOnly, openWorld, non-idempotent and non-destructive. The description adds one genuine behavioral guarantee beyond them – content is not persisted locally – plus the constraint that only explicitly read-only tools may be called. It says nothing about failure modes, what happens when a named tool doesn't exist, or how results are returned.

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?

A single sentence with no filler, and the safety-relevant constraint is front-loaded. It is efficient but slightly under-specified rather than padded.

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 a nested free-form argument object, zero schema description coverage, and no output schema, the description leaves too much unsaid: how to obtain a valid tool name, what shape arguments must take, and what a call returns. The one-line description cannot carry the full burden for a dynamic-dispatch tool.

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 coverage is 0% and both parameters are undocumented in both places. The description never explains that 'name' is the identifier of a tool previously discovered (and presumably matching mobbin_list_tools output) or that 'arguments' is a free-form object passed through to that tool. For a passthrough tool with a nested open object, this is the critical missing information.

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?

States a specific verb ('Call') and resource (a discovered, read-only official Mobbin MCP tool), which separates it from sibling discovery tools like mobbin_list_tools and mobbin_search_screens. It is clear what the tool does, though it does not name the sibling it pairs with explicitly.

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

Usage Guidelines3/5

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

The word 'discovered' implies this is invoked after enumeration via a listing tool, but the description never states that prerequisite or any when-not conditions. Usage is inferable from the phrase 'explicitly read-only' but not spelled out.

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