Skip to main content
Glama
Chrome Profile Manager

Chrome Profile Manager

by megamen32

profile_list

Lists Chrome profile names and reports controlled, helper, policy, and unmanaged availability; note that backend configuration is not runtime proof.

Instructions

List profile names and report controlled, helper, policy and unmanaged availability; backend configuration is not runtime proof

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "profile_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does add a genuine interpretive caveat — that backend configuration is not runtime proof — which warns the agent not to over-trust the reported availability, but it is silent on read-only guarantees, side effects, and result structure.

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 the verb first and no filler. The tail is dense and jargon-laden ("controlled, helper, policy and unmanaged availability"), which slightly hurts parseability, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter list tool the description covers what categories of information come back, which is more than most. Without an output schema, however, it does not say how names and availability are shaped or whether the listing is truncated, leaving the return format underspecified.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The schema is an empty closed object and the description correctly implies no filtering or input is accepted; nothing further is needed here.

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?

"List profile names" gives a specific verb and resource, and the second clause adds what else is reported (controlled, helper, policy, unmanaged availability). It is clearly the discovery/read entry point among siblings such as profile_install or profile_helper_reconcile, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: as a pure list operation with no parameters, an agent can infer it is the discovery step before install/update/reconcile calls. There is no explicit when-to-use statement, no prerequisite guidance, and no mention of whether this should precede other profile tools.

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