Skip to main content
Glama

adb_profile_save

Save a detected or manually composed Android device profile to the profiles library, including custom quirks and notes for reuse.

Instructions

Save a device profile to the profiles library. Use after adb_profile_detect to persist the profile, or create a manual profile with custom quirks and notes.

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": {
      "name": "<name>",
      "profile": "<profile>"
    },
    "name": "adb_profile_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesProfile name (used as filename)
profileYesProfile JSON string (from adb_profile_detect output or manually composed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses the persistence target (the profiles library) and where profile content originates, but says nothing about overwrite behavior when the name collides with an existing file, failure modes, or what is returned after saving.

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 action and followed by the workflow context. Nothing is redundant, though the closing "custom quirks and notes" phrasing is slightly loose since neither is a distinct parameter.

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 two-parameter write tool with no output schema and no annotations, the description covers purpose, source of input, and workflow position adequately. The main missing piece is collision/overwrite semantics, which matters because the name doubles as a filename.

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%, so both parameters (name as filename, profile JSON string) are already documented. The description reinforces that the profile value comes from detect output or hand composition, which is useful context, but adds no format or constraint detail beyond the schema.

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?

"Save a device profile to the profiles library" states a specific verb and resource, and naming adb_profile_detect as the upstream step separates it from the detect/list siblings. It does not explicitly contrast with adb_profile_list, so it stops short of full sibling differentiation.

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 gives two concrete entry paths: persist output from adb_profile_detect, or compose a profile manually. That is clear when-to-use guidance tied to a named alternative, but there is no when-not guidance (e.g., what to do if a profile with that name already exists).

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