Skip to main content
Glama
Chrome Profile Manager

Chrome Profile Manager

by megamen32

profile_helper_reconcile

Resolve a pending helper operation for a Chrome profile and extension without repeating the reload, completing helper state after profile or extension changes.

Instructions

Reconcile a pending helper operation without repeating reload

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>",
      "extension_id": "<extension_id>"
    },
    "name": "profile_helper_reconcile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_idYes
extension_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/5

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

No annotations, so the description carries the full burden. It discloses only that the call avoids a repeat reload; whether the operation mutates state, requires prior staging, errors when nothing is pending, or is safe to retry is unstated.

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?

A single short front-loaded clause with no filler, but the brevity comes at the cost of specification rather than achieved efficiency.

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 state-mutating reconciliation tool with no annotations, no output schema, and zero parameter documentation needs far more description than one clause to be callable correctly.

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% and both parameters (profile_id, extension_id) are undocumented in the schema. The description adds no meaning such as what identifiers they expect, whether extension_id scopes the reconcile, or what happens if the pair is mismatched.

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

Purpose2/5

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

"Reconcile a pending helper operation" mostly restates the tool name (profile_helper_reconcile) and leaves "helper operation" and "pending" undefined. It never says what state is being reconciled or how it differs from the sibling profile_reconcile.

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?

The phrase "without repeating reload" hints at a context (you already have state loaded), but there is no explicit when-to-use, when-not-to-use, or routing to profile_reconcile / profile_helper_reload / profile_helper_rollback.

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