Skip to main content
Glama
Chrome Profile Manager

Chrome Profile Manager

by megamen32

profile_reload

Reloads an unpacked Chrome extension in a paired profile through the controlled pipe backend, then verifies the loaded version matches the expected version.

Instructions

Reload through a controlled pipe backend and verify loaded version

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>",
      "expected_version": "<expected_version>"
    },
    "name": "profile_reload"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_idYes
extension_idNo
expected_versionYes

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. It mentions a 'controlled pipe backend' and version verification, but does not state whether reload is disruptive, what permissions are required, whether it is reversible, or how failures are handled.

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?

The definition is a single front-loaded sentence with no redundant wording. It is appropriately sized, though the phrase 'controlled pipe backend' adds ambiguity rather than useful precision.

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 an unannotated reload operation with three undocumented parameters and no output schema, the description is too thin. It should explain the operational impact of reload and what the verification step actually confirms.

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 the description needs to compensate but mostly does not. 'Verify loaded version' loosely hints at expected_version, but profile_id and extension_id are unexplained in role, format, or constraints.

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 description names a specific action (reload) and a verification step, which gives some sense of purpose. However, the resource is only implied by the tool name, and 'controlled pipe backend' is opaque jargon that does not distinguish this from profile_helper_reload.

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?

There is no guidance on when to use this tool versus profile_helper_reload or other siblings such as profile_reconcile or profile_rollback. No prerequisites or exclusions are stated, leaving usage to be inferred from the name alone.

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