Skip to main content
Glama
Sign In
agy-profiles

agy-profiles

by harrymove-ctrl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

profile_list

Lists all isolated Antigravity sandbox profiles, host binaries, and live status so you can inspect available environments and their current state.

Instructions

List all isolated Antigravity sandbox profiles, host binaries, and live status.

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.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does signal read-only enumeration and hints that results include runtime 'live status' (implying probing rather than cached data), but it says nothing about cost/latency, permissions, or ordering.

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 wasted wording that enumerates exactly what the call surfaces.

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

Completeness4/5

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

For a zero-argument listing tool with no output schema, stating the three categories of returned items is close to sufficient. A brief note on empty-result behavior or ordering would close the remaining gap.

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 applies; there are no argument semantics that the description needs to explain.

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?

Specific verb ('List') plus concrete resources ('isolated Antigravity sandbox profiles, host binaries, and live status'). It is clearly distinguishable from single-profile siblings like profile_inspect, though it never names them 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 verb 'List' implies a discovery/enumeration use case, but there is no explicit when-to-use statement, no pointer to profile_inspect for details on a single profile, and no note that no filtering arguments exist.

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