Skip to main content
Glama

Renew the lease

emu_renew
Idempotent

Extend this session's lease on a shared Android emulator (AVD), even after it expired, to keep the device reserved; it fails when no lease exists or another session owns it.

Instructions

Extend this session's lease of the AVD (default 4 hours from now), also after it ran out. Refused with NO_LEASE when there is no lease (take it with emu_start) and NOT_OWNER when the lease is another session's (then the emulator is busy: wait or ask the person). Does not touch the device.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "emu_renew"
  }
}

Input Schema

NameRequiredDescriptionDefault
avdNoAVD name (default "unity-test", or the EMU_AVD environment variable of the server).
hoursNoLease length in hours from now (default 4).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing both refusal modes and their remedies, the default extension window, and the scope limit "Does not touch the device" — important because readOnlyHint=false otherwise signals a state mutation of unknown blast radius. It does not say whether repeated renewals compound or reset the window (schema and annotations imply reset/idempotent), so the description stops just short of fully closed.

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?

Short and front-loaded: the action and default come first, then the failure routing. The parenthetical asides and stacked clauses in the middle sentence make it slightly dense, but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-optional-parameter, no-output-schema tool, the description covers action, defaults, error conditions, remediation and side-effect scope — everything needed to call it correctly and to recover from failure.

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 both parameters already document their defaults, ranges and semantics, so the schema carries the load. The description adds the "from now" framing of the lease window, which is mild corroboration rather than new meaning; baseline 3 applies.

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?

States a specific verb and resource ("Extend this session's lease of the AVD") with the default duration, and explicitly distinguishes itself from the lease-acquisition sibling by naming emu_start. An agent can tell this apart from emu_start/emu_release without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use (extending, including after expiry) and names the alternative path (take a lease with emu_start) plus the remediation when the lease belongs to another session — wait or ask the person. Failure routing is fully spelled out with the concrete error codes NO_LEASE and NOT_OWNER.

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