Skip to main content
Glama
Sign In
agy-profiles

agy-profiles

by harrymove-ctrl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

profile_clone

Clone a stopped sandbox profile to a new slug and assign a freshly locked .zshenv HOME for isolated reuse.

Instructions

Clone a stopped sandbox profile to a new profile slug with freshly locked .zshenv HOME.

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": {
      "source": "<source>",
      "target": "<target>"
    },
    "name": "profile_clone"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNo
sourceYes
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 disclosure burden. It does reveal the stopped-source precondition and that the clone gets a "freshly locked .zshenv HOME", which is useful behavioral detail. But it omits collision handling for an existing target slug, permission requirements, reversibility, and whether the new profile inherits packages or state — significant gaps for a state-mutating operation with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the precondition and result are packed in without redundancy.

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?

No output schema and no annotations mean the description is the only source of behavior, yet it leaves the label parameter, error conditions, and post-clone state undefined. For a three-parameter mutation tool with 0% schema documentation, this is not complete enough for confident invocation.

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

Parameters3/5

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

Schema coverage is 0%, so the description must compensate for all three parameters. It adds real meaning for the two required ones: source must be a stopped sandbox profile and target is a new profile slug. The optional "label" parameter is never mentioned in the description or schema, leaving it entirely unexplained.

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?

"Clone a stopped sandbox profile to a new profile slug" gives a specific verb and resource, and the word "clone" distinguishes it from profile_create, which presumably builds from scratch. It falls short of 5 because no sibling is named to anchor the distinction 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?

The phrase "stopped sandbox profile" supplies an implicit precondition (the source must be stopped), which is genuine usage guidance. However, there is no explicit when-to-use versus profile_create or profile_update, and no statement about what to do if the source is running or the target already exists.

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

Deploy Server

Other Tools