Skip to main content
Glama
Chrome Profile Manager

Chrome Profile Manager

by megamen32

profile_helper_stage

Validates and stages an immutable extension artifact for a verified paired Chrome profile, so the artifact is checked and prepared before use.

Instructions

Validate and stage an immutable artifact for a verified paired existing profile

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>",
      "source_path": "<source_path>",
      "extension_id": "<extension_id>",
      "version": "<version>",
      "digest": "<digest>"
    },
    "name": "profile_helper_stage"
  }
}

Input Schema

NameRequiredDescriptionDefault
digestYes
versionYes
profile_idYes
source_pathYes
extension_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/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 behavioral burden, and it only states that the tool validates and stages an immutable artifact. It does not disclose what validation entails, what happens on validation failure, whether staging is reversible, what permissions are required, or what side effects occur. These are material gaps for a mutation-oriented tool.

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 description is a single compact sentence with no filler, and it front-loads the core actions of validating and staging. The dense jargon reduces clarity, but there is no unnecessary wording or structural bloat.

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 tool with five required parameters, no annotations, no output schema, and 0% schema description coverage, this one-sentence description is too thin. It provides only partial context about validation and staging without explaining parameter roles, failure behavior, or return expectations. It is inadequate for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All five required parameters have 0% schema description coverage, and the description does not map any of profile_id, source_path, extension_id, version, or digest to their meaning, format, or role. It only vaguely implies an artifact and a profile, adding essentially no semantic detail beyond the parameter names. The description does not compensate for the schema coverage gap.

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 uses a specific verb pair, "validate and stage," and names a resource, "immutable artifact." However, the qualifying phrase "for a verified paired existing profile" is opaque, and it does not clearly differentiate this helper from siblings such as profile_stage. The general purpose is inferable, but the exact role remains vague.

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 explicit when-to-use guidance, no alternatives named, and no clear prerequisites beyond the ambiguous phrase "verified paired existing profile." An agent cannot confidently choose between this helper and profile_stage or the other profile_helper_* tools. Usage must be guessed rather than derived.

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