Skip to main content
Glama
Sign In
agy-profiles

agy-profiles

by harrymove-ctrl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

launcher_remove

Removes the macOS .app launcher shim tied to a sandbox profile, enabling cleanup of unused profile launchers.

Instructions

Remove the macOS .app launcher shim associated with a sandbox 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": {
      "name": "<name>"
    },
    "name": "launcher_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
destNo
nameYes
targetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 disclosure burden. It says what is removed but not whether removal is destructive or irreversible, what permissions are required, what happens if the shim does not exist, or whether other sandbox artifacts are affected.

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 efficient sentence with the operation front-loaded. It is appropriately concise, though its brevity contributes to the missing behavioral and parameter detail rather than compensating for it.

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 mutation tool with no annotations, no output schema, and three undocumented parameters, the definition is substantially incomplete. An agent could identify the broad intent but would lack the information needed to call it safely and correctly.

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?

Schema description coverage is 0% for three parameters, and the description does not explain any of them. It only implies the shim relates to a sandbox profile, leaving the required name, optional dest, and hub/ide target enum entirely undocumented in both schema and description.

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?

The description states a specific verb and resource: remove the macOS .app launcher shim associated with a sandbox profile. It is clear what is being removed, though it does not explicitly distinguish this operation from siblings such as launcher_build or profile_delete.

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 guidance on when to use this tool versus alternatives, nor any prerequisites or warnings. It does not say when removal is appropriate, whether a build must exist first, or how this differs from deleting a profile.

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