Mobile Automator MCP Server

Overview Schema Source Related Servers Discussions Admin

Verify Network Payload

verify_network_payload

Read-onlyIdempotent

Verify network response payloads by asserting JSON fields via dot/bracket paths—check equality, containment, existence, type, and minimum length.

Instructions

Assert JSON response fields via dot/bracket paths: equals, contains, exists, type, minLength. More flexible than verify_sdui_payload, which only supports exact field matching.

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": {
      "sessionId": "<sessionId>",
      "responseAssertions": "<responseAssertions>"
    },
    "name": "verify_network_payload"
  }
}

Input Schema

Name	Required	Description
`url`	No	Exact or partial URL; use this OR matcher
`matcher`	No	Matcher to locate the event; use this OR url
`sessionId`	Yes	Active or completed session ID
`filterDomains`	No	Optional Proxyman domain filter
`responseAssertions`	Yes	Path-based assertions to evaluate on the response body

Output Schema

Name	Required	Description	Default
`event`	No
`passed`	Yes
`verdict`	Yes
`mismatches`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 28, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description's behavioral disclosure is less critical. The description adds path-based assertion context but no additional behavioral details like error handling or edge cases.

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?

The description is a single, well-structured sentence that front-loads the purpose and efficiently adds a sibling comparison. No wasted words.

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 rich input schema and output schema, the description adequately conveys the core functionality. It doesn't explain all parameter interactions but is sufficient for an agent to understand the tool's basic use.

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?

All 5 parameters have schema descriptions (100% coverage), so the description adds minimal extra meaning beyond the schema. The description lists assertion types but the schema already specifies them.

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 verb 'Assert' and the resource 'JSON response fields via dot/bracket paths'. It lists supported assertions and distinguishes from the sibling tool verify_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?

The description explicitly compares with verify_sdui_payload, providing a clear when-to-use alternative. However, it does not elaborate on other usage conditions or prerequisites, so not a 5.

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