Skip to main content
Glama
Sign In
Karagöz

Karagöz

by yagizdo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Remove karagoz's iPhone runner

uninstall_runner
Destructive

Removes Karagöz's runner and its provisioning profile from an iPhone, cleaning up automation components using the device ID or name.

Instructions

Remove karagoz's runner and its provisioning profile from an iPhone.

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": "uninstall_runner"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoId or name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description does add real value by disclosing that the provisioning profile is removed alongside the runner — a non-obvious side effect — but it omits whether this is reversible, what happens if no runner is present, or whether the device can be resolved implicitly.

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 side effect is attached directly to the action. Slightly undermined by the unexplained hardcoded owner name.

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 one-parameter destructive tool with annotations and no output schema, the description covers the essentials, but it leaves open the failure modes (no runner installed, device lookup) and the fixed 'karagoz's' qualifier is unexplained, so an agent cannot tell whether it must supply that owner.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already documents 'device' as an id or name. The description adds nothing about the device argument or its fallback behavior, which is acceptable at baseline but no better.

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?

States a specific verb (Remove) and a specific resource (the runner and its provisioning profile) plus the target environment (an iPhone), which separates it from the plain 'uninstall' sibling. The hardcoded owner name 'karagoz's' reads as a template artifact rather than a meaningful scope qualifier.

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 by the name pairing with install_runner; there is no statement of when to prefer this over uninstall, or what preconditions apply (runner currently installed, device reachable). An agent can infer the flow but must guess.

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