Skip to main content
Glama
Chrome Profile Manager

Chrome Profile Manager

by megamen32

profile_install

Installs a staged Chrome profile with compare-and-swap version checks to apply controlled changes to a paired Chrome setup.

Instructions

Install a staged controlled profile with CAS

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_install"
  }
}

Input Schema

NameRequiredDescriptionDefault
stage_idYes
profile_idYes
expected_versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure for a mutation. It does not say what CAS / expected_version does on a version mismatch, whether the operation is atomic or reversible, what permissions or preconditions are required, or what happens to existing state on failure.

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

Conciseness3/5

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

It is a single front-loaded phrase with no wasted wording, but the brevity is under-specification rather than efficiency. The one appended qualifier, "with CAS", adds ambiguity instead of clarity.

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?

A mutation tool with two required parameters, no annotations, and no output schema needs the description to cover prerequisites, conflict semantics, and results. The description is a single fragment that leaves all of that 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% across three parameters, so the description must compensate and does not. It never explains what profile_id or stage_id identify, nor that expected_version is the compare-and-swap token implied by "CAS" — the one inference an agent must get right.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "Install a staged controlled profile with CAS" gives a verb (install) and a resource (a staged profile), but both "controlled profile" and "CAS" are unexplained jargon. It does not distinguish this from siblings such as profile_stage or profile_helper_stage, so an agent cannot tell from the text which one actually performs the install.

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

Usage Guidelines2/5

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

"Staged" hints that a staging step must happen first, but no prerequisite is stated and no alternative is named. There is no guidance on when to use this versus profile_helper_prepare, profile_reconcile, or profile_rollback, or on when not to use it.

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