Skip to main content
Glama
Chrome Profile Manager

Chrome Profile Manager

by megamen32

profile_stage

Stage Chrome extension content from a relative artifacts path, confirming hash, key-derived identity, and version for profile management.

Instructions

Stage content from a relative path under the manager artifacts directory; verify hash, key-derived identity and 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>",
      "source_path": "<source_path>",
      "extension_id": "<extension_id>",
      "version": "<version>",
      "digest": "<digest>"
    },
    "name": "profile_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.7/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose that the tool verifies hash, key-derived identity and version, which is useful, but it never says whether staging writes files, whether it overwrites existing staged artifacts, what happens when verification fails, or whether permissions are required. For an unannotated mutation-style tool that is a substantial gap.

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 front-loaded sentence with no filler; the verb and scope come first and the verification behavior follows. It is efficient, though its terseness borders on under-specification rather than true economy.

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?

Five required parameters, zero schema description coverage, no annotations and no output schema demand considerably more than one sentence. The description never explains where staged content ends up, what the verification result means to the caller, or how failures surface.

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 five required parameters, so the description must compensate. It does add the key constraint that source_path is relative to the manager artifacts directory and hints that digest/version are verification targets, but it does not say which parameter carries identity (profile_id vs extension_id), nor give formats for digest or version.

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

Purpose4/5

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

"Stage content from a relative path under the manager artifacts directory" names a specific verb and a precise resource location, and adds the verification steps (hash, key-derived identity, version). It is clear what the operation does, but it offers no differentiation from the near-identical sibling profile_helper_stage, which an agent could easily confuse it with.

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 or when-not-to-use guidance, and no alternatives are named. The only implied context is that content is being staged prior to some later activation, which the agent must infer from the sibling names rather than from this definition.

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