Skip to main content
Glama
Sign In
orion-phone-mcp

orion-phone-mcp

by OrionArchitekton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

release

Return a leased Android emulator phone when done, freeing it for other agents; a locked phone shuts down.

Instructions

Give the phone back as soon as you are done: until then, or until the lease expires, no other agent can use it. Releasing a locked phone shuts it down.

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": {
      "phone": "<phone>"
    },
    "name": "release"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the exclusive-lock effect ('no other agent can use it'), the lease-expiry fallback, and a destructive side effect ('Releasing a locked phone shuts it down'). It does not cover auth/permission requirements, which is the main remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action and free of filler. The exclusivity and shutdown details are valuable, not padding.

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 one-parameter tool with an output schema covering return values, the description explains the important effects (exclusive lock, expiry, shutdown). Only the phone-argument semantics and any precondition on holding a lease are missing.

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 the single 'phone' parameter, and the description never explains what value to pass (ID, name, handle) or any format. The parameter is inferable from context but is substantively undocumented in both schema and description.

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 states a concrete action ('Give the phone back') and immediately explains the resource and its exclusivity semantics. It effectively distinguishes the release action from the leasing concept implied by the sibling 'lease', though it never names that sibling 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?

'Give the phone back as soon as you are done' gives a timing cue, but there is no explicit statement of preconditions (must hold a lease first) or a named alternative. The usage context is implied rather than spelled out.

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