Skip to main content
Glama
jegriffi91

Mobile Automator MCP Server

by jegriffi91

Verify SDUI Payload

verify_sdui_payload
Read-onlyIdempotent

Validate an SDUI response payload against expected fields. Returns match status and any mismatches to confirm correct UI rendering.

Instructions

Validate that a specific SDUI network response matches expected fields. Returns matched status and a list of any mismatches. Used to assert correct server-driven content is rendered by the UI.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe full URL of the SDUI endpoint to verify
sessionIdYesActive or completed session ID
filterDomainsNoOptional list of domains to pre-filter the Proxyman HAR export (e.g., ["api.myapp.com"])
expectedFieldsNoKey-value pairs that must be present in the response payload

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
actualNoThe actual response payload
matchedYesWhether all expected fields matched the actual response
mismatchesNoList of field paths that did not match expectations
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive nature. Description adds return behavior (matched status, mismatches). No contradictions.

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 sentences, no fluff, front-loaded with purpose. Every sentence is useful.

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?

Given the annotations and schema, description is mostly complete. Briefly mentions return value. Could clarify that filterDomains relates to Proxyman, but not essential.

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% with parameter descriptions. The tool description does not add additional semantic meaning beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool validates an SDUI network response against expected fields and returns matched status and mismatches. It distinguishes from sibling network verification tools by specifying 'SDUI payload'.

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

Usage Guidelines4/5

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

States it is used to assert correct server-driven content rendering, providing context. However, it does not explicitly contrast with other verification tools or give when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jegriffi91/mobile-automator-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server