sa-ecosystem-node

Get fleet

get_fleet

Read-onlyIdempotent

Read a public fleet by address or list fleets owned by a player profile on the z.ink test realm. Read-only.

Instructions

Read one public fleet by account address, or list fleets owned by a player profile, on the z.ink test realm. Read-only.

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

Input Schema

Name	Required	Description	Default
`fleetAddress`	No	Fleet account address.
`profileAddress`	No	Player profile address. Lists that profile's fleets when fleetAddress is omitted.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 4, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered without prose. The description still adds genuine context beyond them: results are restricted to public fleets and scoped to the z.ink test realm, which tells the agent what network and visibility boundary it is querying.

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?

A single sentence front-loads the primary operation, then the alternate mode, then the environment and safety tag. Nothing is redundant and no sentence fails to earn its place.

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 two-parameter read tool with full schema coverage, no output schema, and annotations covering safety, the description carries enough to call it correctly. The only missing piece is the zero-parameter case and any hint of result shape or paging, which keeps it short of full completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the schema itself already documents that profileAddress lists fleets when fleetAddress is omitted. The description restates that mapping at a high level without adding syntax, precedence rules, or edge-case behavior, so the baseline of 3 applies.

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 verb and resource ("Read one public fleet") plus a second mode ("list fleets owned by a player profile"), so an agent knows exactly what comes back. It does not name a sibling to contrast with, but no sibling in the provided list covers fleets, so disambiguation is implicitly handled.

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 "by account address, or list fleets owned by a player profile" phrasing implies which parameter selects which mode, giving usable context. However, both parameters are optional, and the description never says what happens when neither is supplied or how to choose a mode deliberately — that gap leaves a real inference for the agent.

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