Skip to main content
Glama
Sign In
AutoMobile

AutoMobile

by zillow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

setAppSource

Configure source code directory and platform for mobile apps in the AutoMobile automation suite. Specify app ID, source path, and target platform (Android or iOS) for test execution.

Instructions

For a given appId, set the source code path and platform.

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": {
      "sourceDir": "<sourceDir>",
      "appId": "<appId>",
      "platform": "<platform>"
    },
    "name": "setAppSource"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceDirYesApp source code directory.
appIdYesApp ID to persist these settings for.
platformYesPlatform the app is built for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a mutation ('set'), but doesn't specify if this requires specific permissions, whether changes are reversible, or what happens on success/failure. This is inadequate for a mutation tool with zero annotation coverage.

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, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't cover behavioral aspects like side effects, error handling, or return values, leaving significant gaps in understanding how to use the tool effectively in context.

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?

The schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description adds no additional meaning beyond what's in the schema, such as explaining interactions between parameters or usage examples, resulting in the baseline score for high schema coverage.

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?

The description clearly states the action ('set') and the target ('source code path and platform') for a specific resource ('appId'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from potential siblings like 'installApp' or 'resetConfig', which might involve app-related operations, so it misses full sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives, such as whether it's for initial setup, updates, or specific contexts like development vs. testing. It also lacks prerequisites, like needing an existing app or device configuration, leaving usage unclear.

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