Skip to main content
Glama
Chrome Profile Manager

Chrome Profile Manager

by megamen32

profile_reconcile

Read back a pending Chrome profile or extension operation without repeating it, so you can confirm status before making changes.

Instructions

Read back a pending operation without repeating 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>"
    },
    "name": "profile_reconcile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_idYes
extension_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose one useful trait — the call is non-repeating, i.e. it observes rather than re-triggers a pending operation. It says nothing about what state is returned, whether it blocks or errors when nothing is pending, or what permissions are needed for a tool whose name implies reconciliation.

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?

A single short, front-loaded sentence with no padding. Brevity is achieved, though partly by omitting content the description should have carried.

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?

With no annotations, no output schema, and undocumented parameters, the description is too thin for a tool whose name implies a reconcile/recovery role. An agent lacks the scope, return-value, and failure-mode information needed to call it confidently.

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% for two parameters, so the description must compensate and does not. It never mentions profile_id (required) or extension_id (optional), nor whether omission of extension_id broadens the read to all extensions.

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 does state a verb and object ('read back a pending operation'), which is more specific than the name alone, but it sits oddly against the name 'profile_reconcile', which suggests a reconciliation/mutation step. An agent cannot tell from this text whether the tool reconciles state, re-checks status, or resolves a pending operation — only that reading is involved.

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?

No when-to-use condition, no prerequisites, and no named alternative among the many profile_helper_* / profile_* siblings. 'Without repeating it' hints at a post-stage check, but the agent must infer that entirely.

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