Skip to main content
Glama
Chrome Profile Manager

Chrome Profile Manager

by megamen32

profile_helper_prepare

Prepares a profile-owned directory from an immutable stage without installing it, so you can set up a Chrome profile for extension inspection and management.

Instructions

Prepare a profile-owned directory from an immutable stage; does not install it

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": {
      "profile_id": "<profile_id>",
      "stage_id": "<stage_id>"
    },
    "name": "profile_helper_prepare"
  }
}

Input Schema

NameRequiredDescriptionDefault
stage_idYes
profile_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses one important boundary — this does not install — but says nothing about whether it creates or overwrites an existing directory, what happens to prior contents, whether it is idempotent, or what permissions are needed for a filesystem-mutating operation.

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?

A single compact sentence with the action front-loaded and the exclusion clause at the end. Every clause carries information and nothing is padded.

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 two-required-parameter, no-annotation, no-output-schema tool that mutates a directory, the definition omits too much: failure modes, effect on existing directories, and the relationship to the install/stage siblings. Only the negative scope is covered.

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%, so both required parameters (profile_id, stage_id) are undocumented in the schema. The description only obliquely hints that stage_id identifies an 'immutable stage' and profile_id an owned profile; it adds no format, sourcing, or validity constraints, so it fails to compensate for the coverage gap.

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?

States a specific verb ('prepare') and resource ('profile-owned directory') plus the source ('immutable stage'), and the trailing 'does not install it' rules out the most likely confusion with profile_install. It is clear what the tool acts on, though the sibling it contrasts with is not named explicitly.

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 phrase 'does not install it' implies the tool is a non-committal setup step to be used before install, which is useful implied guidance. However, no explicit when-to-use, when-not-to-use, or named alternative (e.g. profile_stage vs profile_install) is given, leaving the agent to infer the ordering.

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