Skip to main content
Glama
Sign In
agy-mcp

agy-mcp

by cyeezy08
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

agy_help

List all available agy-mcp tools and their usage instructions to quickly find the right tool for your Antigravity IDE tasks.

Instructions

Show all available agy-mcp tools and usage.

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

Input Schema

NameRequiredDescriptionDefault
ctxNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are present, so the description carries the behavioral burden. 'Show' clearly indicates a read-only, non-mutating operation, but the description does not disclose any additional behavioral traits such as output format, permissions, or side effects.

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 filler. It earns its place by stating the tool's core function directly.

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 simple read-only help tool with no required parameters and an output schema, the description is largely complete. It would benefit from at least a passing mention of the optional ctx parameter, but the tool itself is low-complexity.

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?

The schema has one optional parameter, 'ctx', with 0% description coverage. The tool description does not mention it at all, leaving an agent without any guidance on what to pass or whether it matters.

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 uses a clear verb and resource: 'Show all available agy-mcp tools and usage.' It communicates the tool's scope precisely, although it does not explicitly contrast with sibling tools like agy_list_skills or agy_get_config.

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 description implies the tool is for discovering the full set of agy-mcp tools and their usage, which is a reasonable when-to-use signal. However, it does not explicitly name alternatives or state when not to use this tool.

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