GravityPort

asset_get

Read-only

Retrieve a saved asset with its full prompt recipe and metadata. Use when compact summaries from asset_list or asset_search lack the complete recipe needed to reuse the asset.

Instructions

Get one saved asset and its full prompt recipe. asset_list and asset_search return only compact summaries; call this for the full recipe and metadata.

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": {
      "assetId": "<assetId>"
    },
    "name": "asset_get"
  }
}

Input Schema

Name	Required	Description	Default
`assetId`	Yes

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 contributes beyond that by declaring the payload shape (full prompt recipe plus metadata) versus the truncated form returned by siblings, which is the key behavioral difference for output expectations. It omits not-found/error behavior, keeping it short of a 5.

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 sentences, zero filler. The primary action and return payload are front-loaded, with the sibling differentiation following as supporting context.

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 single-parameter read tool with full annotation coverage and no output schema, the description supplies what an agent needs about purpose and result shape. The remaining gap is the identity/format of 'assetId' and behavior when the asset does not exist, which is a minor but real omission.

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% for the single required 'assetId' parameter, so the description carries the full burden — yet it never states the identifier format (id versus name), where the value is obtained, or whether a slug is accepted. The only hint is the reference to asset_list/asset_search returning summaries, which weakly implies the id originates there.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Get one saved asset and its full prompt recipe') and immediately contrasts that with what asset_list and asset_search return (compact summaries). An agent can distinguish this retrieval-by-id tool from the sibling listing/search tools without opening any schema.

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?

It gives an explicit routing rule: use this when the full recipe and metadata are needed rather than a summary. It does not state what to do on a miss or that the identifier should come from a prior list/search call, but the positive guidance is clear and actionable.

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