Skip to main content
Glama

transport_update

Apply partial status, phase, or notes updates to an existing transport run to transition it through lifecycle states.

Instructions

Update a public transport run.

    Applies partial status, phase, notes, error, or summary updates to an existing run and appends an event with
    the changed fields.

    When to use:
    - Move a run from queued to running, returned, failed, or another public lifecycle state.
    - Attach status notes from an external runtime.

    When NOT to use:
    - Do not use this to write report artifacts; use transport_submit_report.
    - Do not use this for brief draft lifecycle changes.

    Examples:
    >>> transport_update("transport-20260506120000-a1b2c3d4", status="running")
    {"runId": "transport-...", "status": "running", "phase": "running", ...}
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoOptional error text.
notesNoOptional human-readable notes.
phaseNoOptional phase transition.
run_idYesTransport run id to update.
statusNoOptional status transition.
summaryNoOptional short result summary.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description carries full burden. It discloses that the tool performs partial updates and appends an event with changed fields, indicating mutation. However, it does not mention idempotency, error handling (e.g., missing run), or authorization requirements, which would strengthen clarity.

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 description is concise and well-structured: a one-line summary, bulleted when-to/when-not guidelines, and an example. Every sentence is informative with no wasted words.

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?

The description adequately covers purpose, usage, and examples. It mentions updating an 'existing run' but could be more explicit about the need for a valid run_id. Since output schema exists, return value explanation is not required. Overall, it is fairly complete for the tool's complexity.

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?

All six parameters have full schema descriptions (100% coverage). The description adds value by clarifying 'partial updates' and listing the updatable fields (status, phase, notes, error, summary) in context, plus a concrete example demonstrating usage with status='running'.

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 clearly states the tool updates a public transport run with specific fields (status, phase, notes, error, summary) and appends an event. It explicitly distinguishes from transport_submit_report for writing report artifacts, differentiating it from a sibling tool.

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

Usage Guidelines5/5

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

The description includes explicit 'When to use' and 'When NOT to use' sections, listing valid scenarios (e.g., moving run to a new lifecycle state, attaching status notes) and excluding report writing and brief draft changes, with a direct alternative (transport_submit_report).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nograai/nogra-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server