Skip to main content
Glama
Sign In
mobile-freecode

mobile-freecode

by zunairvf-sys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_device

Retrieve detailed device information, including capabilities, connection state, and current foreground app, to assess device status before automating actions.

Instructions

Get detailed information about a specific device, including capabilities, connection state, and current foreground app.

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

Input Schema

NameRequiredDescriptionDefault
deviceYesDevice ID (e.g. fc-001) or name (e.g. "Zunair's Galaxy S24")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the kind of data returned (capabilities, connection state, foreground app), which is useful, but it does not state that the operation is read-only, mention error conditions, or note whether the device must be paired/online.

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?

One sentence, front-loaded with the action, and every clause adds value by listing the specific details returned. No filler or redundancy.

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?

For a single-parameter getter with no output schema, the description is nearly sufficient. It names the key return fields, but omits possible error handling or device availability constraints. Overall, an agent can call this correctly with minimal guesswork.

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% and the schema already describes the device parameter with examples. The description adds no additional semantic information about the parameter, matching the baseline for complete schema coverage.

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 states a clear verb ('Get') and resource ('a specific device'), and distinguishes itself from list_devices by targeting one device rather than all. The mention of capabilities, connection state, and foreground app makes the function unambiguous.

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 description implies usage when you need details on a single known device, contrasting with listing, but it does not explicitly name alternatives or state when not to use it. No exclusions or prerequisites are provided.

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