Skip to main content
Glama
Sign In
Mobile Design MCP

Mobile Design MCP

by noxpublishing
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

search_apps

Read-onlyIdempotent

Search a local award/curated app catalog with full-text metadata queries; filter by iOS/Android and awards to find mobile design references, not full screen libraries.

Instructions

Search the local award/curated app catalog with FTS5. This is metadata search, not a full screen library.

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": "search_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
platformNo
awardsOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds useful context that this is FTS5-based metadata matching against a local curated catalog, but it does not disclose query syntax, ranking behavior, or what fields come back.

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?

Two short sentences with no waste, the primary action front-loaded and the disambiguation immediately after.

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 four-parameter search tool with zero schema descriptions and no output schema needs the description to explain query form, platform/awardsOnly filtering, and result shape. It covers none of these, leaving an agent to guess at parameter behavior.

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% for four parameters. The description never mentions limit, platform, awardsOnly, or query, and gives no query syntax even though FTS5 implies non-obvious matching rules; 'award/curated' only faintly hints at awardsOnly.

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+resource (search the local award/curated app catalog) and adds an implementation detail (FTS5). The clause 'not a full screen library' signals it is different from screen-search siblings, though it does not name mobbin_search_screens directly.

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?

'This is metadata search, not a full screen library' implies the alternative for screen search without naming it or stating when each should be chosen. No positive usage context (e.g., use when you need app-level metadata vs. screenshots) is given.

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