Skip to main content
Glama
Sign In
starshipit-mcp

starshipit-mcp

by devkindhq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Manifest Files

starshipit_get_manifest_files
Read-onlyIdempotent

Retrieve manifest document files as base64 content, optionally filtered by manifest ID, to download carrier pickup PDFs or list available documents.

Instructions

Retrieve manifest documents (PDF, XML, etc.) as base64 file content.

Each manifest can have one or more associated document files that you submit to the carrier at pickup. The markdown format lists file names and sizes. The full base64 content is always in structuredContent; the JSON text output is capped at 25000 characters.

Query parameters:

  • manifest_id (optional): Filter to files for a specific manifest. Omit to list files across all manifests.

  • limit: Max results per page (default 50, max 250)

  • page: Page number (default 1)

Returns:

  • files: Array of { file_name, file_data }, where file_data is the base64 file content

Error cases:

  • 404: Manifest ID not found

  • 401/403: Invalid or missing API credentials

Use this tool when:

  • Downloading a manifest PDF to hand to a carrier driver

  • Retrieving document URLs for a specific manifest ID

  • Listing all available manifest documents

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination (default: 1)
limitNoMaximum number of results to return (default: 50, max: 250)
manifest_idNoFilter by a specific manifest ID — omit to return files for all manifests
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown

Output Schema

NameRequiredDescriptionDefault
errorsNoValidation or processing errors returned by StarShipIt
objectNoThe response payload when StarShipIt returns a non-object value
successNoStarShipIt success flag (a boolean on most endpoints)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: JSON text output is capped at 25000 characters while full base64 always lives in structuredContent, markdown mode lists only file names and sizes, plus documented 404/401/403 error cases. That truncation disclosure is exactly the kind of gotcha an agent needs. The one flaw is the inconsistent claim about 'retrieving document URLs' when the tool returns base64 content, which muddies the behavioral picture.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then cleanly sectioned into parameters, returns, errors, and use cases. Slightly verbose and it repeats pagination defaults already in the schema, and the 'document URLs' line is both inaccurate and unnecessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only filtered-list tool with an output schema and full annotation coverage, the description supplies everything missing: response shape, format-dependent truncation, error semantics, and selection criteria. Nothing an agent needs to invoke it correctly is absent.

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 100%, so baseline would be 3, but the description adds meaning for response_format by explaining what markdown vs JSON actually produce and where the full payload lives. It also restates the manifest_id omit-to-list-all semantics and limit/page defaults, which is duplicative but harmless.

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: 'Retrieve manifest documents (PDF, XML, etc.) as base64 file content.' An agent can distinguish this from starshipit_list_manifests, but the description never names or contrasts that sibling explicitly, so differentiation is inferred rather than stated.

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?

A dedicated 'Use this tool when' block gives three concrete triggering scenarios (handing a PDF to a carrier driver, pulling docs for a manifest ID, listing all docs). No when-not-to-use guidance or named alternative (e.g., list_manifests) is provided, so it stops short of full routing clarity.

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

Deploy Server

Other Tools