GravityPort

stack_get

Read-only

Retrieve a stack's name, cover image, member count, and ordered member asset IDs while excluding trashed or archived members.

Instructions

Read one stack: its name, cover, member count, and member asset IDs in stack order. Members in Trash or archived are left out.

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": {
      "stackId": "<stackId>"
    },
    "name": "stack_get"
  }
}

Input Schema

Name	Required	Description	Default
`stackId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.11Nov 11, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare this as a safe read-only operation. The description adds useful behavior beyond that by specifying which fields are returned, that member asset IDs are in stack order, and that members in Trash or archived are excluded.

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 definition is two tight sentences, front-loaded with the operation and followed by the return contents and exclusion rule. Every sentence contributes directly to correct invocation or interpretation.

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 tool with no output schema, the description usefully summarizes the returned fields and filtering behavior. It is nearly complete, though it should ideally clarify the required stackId parameter or not-found behavior.

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?

The schema has zero description coverage for the required stackId parameter, so the description must compensate. It does not explain what stackId is, how to obtain it, or its expected format, leaving the only parameter semantically under-specified.

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 states a specific operation: read one stack, including its name, cover, member count, and ordered member asset IDs. This clearly differs from stack_list and mutation siblings such as stack_add_assets or stack_rename, though it does not explicitly name those alternatives.

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 phrase 'Read one stack' implies this is the single-stack retrieval tool rather than the list tool, especially given the required stackId. However, it gives no explicit when-to-use guidance, prerequisites, or named alternatives for cases like listing stacks or retrieving asset details.

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