GravityPort

stack_list

Read-only

List stacks in the GravityPort library that have two or more visible members, ordered by most recent update, with optional name filtering.

Instructions

List the stacks shown in the GravityPort library (two or more visible members), most recently updated first, optionally filtered by text in the stack name.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.11Nov 11, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnly, closed-world, and non-destructive behavior. The description adds useful inclusion criteria (two or more visible members) and default sorting (most recently updated first), but does not explain pagination, default limit behavior, or return shape.

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?

One front-loaded sentence with no filler: it gives the resource, scope, ordering, and optional filter efficiently.

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?

Adequate for a simple read-only list tool whose annotations cover safety. However, the undocumented limit parameter and lack of any return-shape note leave gaps for correct invocation.

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 compensate. It explains query as text in the stack name but never explains limit, its default, or whether max 200 is a cap.

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 and resource ("List the stacks") plus scope (GravityPort library, two or more visible members) and ordering. It is clear but does not explicitly differentiate from stack_get or other list tools.

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?

Implied usage is clear: enumerate stacks and optionally filter by stack-name text. No explicit when-to-use, when-not-to-use, or alternative such as stack_get for a single stack is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.