Skip to main content
Glama
Sign In
agy-profiles

agy-profiles

by harrymove-ctrl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

profile_stop

Stops verified running processes owned by a sandbox profile, escalating from SIGTERM to SIGKILL after a timeout. Use it to shut down Antigravity Hub or IDE profiles cleanly.

Instructions

Stop verified running processes owned by a sandbox profile using staged SIGTERM then SIGKILL.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
targetNo
timeout_secNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 usefully discloses the staged SIGTERM-then-SIGKILL sequence, but omits safety details such as irreversibility, permission requirements, timeout behavior, and what happens to processes that ignore SIGTERM.

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?

The description is a single front-loaded sentence with no wasted wording. It communicates the action and mechanism efficiently.

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 destructive process-termination tool with three parameters, no annotations, and no output schema, the description is too sparse. It lacks parameter semantics, safety context, and timeout behavior that an agent would need to invoke it correctly.

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%, so the description must explain the three parameters. It only implicitly maps 'name' to the sandbox profile and does not explain the 'target' enum values (hub, ide, all) or 'timeout_sec'.

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

Purpose5/5

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

The description states a specific verb, resource, and scope: stop running processes owned by a sandbox profile. It also names the termination mechanism, staged SIGTERM then SIGKILL, which clearly distinguishes it from profile-level operations like delete or repair.

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?

It implies the tool is for stopping running processes, but gives no explicit when-to-use guidance or alternatives. It does not say when to use this instead of profile_delete, profile_repair, or other sibling tools.

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