GravityPort

asset_list

Read-only

List saved GravityPort assets for a project, optionally filtered by search text, with compact summaries and cursor-based paging.

Instructions

List saved GravityPort assets for a project, optionally filtered by search text. Returns compact per-asset summaries with the total count (20 per page by default, at most 100; pass cursor to page further); use asset_get for an asset's full recipe and metadata.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.11Nov 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real behavior beyond that: return payload shape (compact per-asset summaries plus total count) and pagination defaults/bounds (20 per page, max 100, cursor to continue).

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?

Two tight sentences with no filler: purpose and return shape first, then the sibling routing pointer. Every clause (page size, cap, cursor) conveys operational information.

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?

With no output schema, the description does the necessary work of characterizing the response (compact summaries, total count) and the paging model, which is what an agent needs to call it correctly. It does not enumerate the summary fields or the shape of the cursor token, but nothing essential is missing for selection or invocation.

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?

Schema description coverage is 0%, so the description must carry the parameter meaning, and it largely does: `query` is search text, `cursor` advances paging, and the 20-default/100-max figures map to `limit`. It stops short of saying whether cursor values are opaque or what happens past the last page, leaving a small gap.

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 saved GravityPort assets for a project") plus the optional search filter, and explicitly contrasts itself with asset_get for full metadata. It does not address how it relates to other listing/search siblings, but the core operation is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear routing rule: use this for compact per-asset summaries, use asset_get when you need an asset's full recipe and metadata. It also explains the paging workflow (pass `cursor`), though it offers no explicit exclusions or guidance on when to omit the query filter.

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