Skip to main content
Glama

transport_register

Register a public transport run to start tracking caller-owned work, allocate artifact paths, and persist state without executing work.

Instructions

Register a public transport run.

    Creates a state-only run record, allocates report/output/log artifact paths under the workspace transport
    substrate, persists state atomically, and appends a transport event.

    When to use:
    - Start tracking caller-owned work through public transport state.
    - Allocate artifact paths before an external runtime begins work.

    When NOT to use:
    - Do not use this to execute work; public transport is state-only.
    - Do not use this for lightweight event logging; use post_event for that.

    Examples:
    >>> transport_register("import-audit", brief_id="brief-123")
    {"schema": "nogra.transport.run.v1", "runId": "transport-...", "status": "queued", ...}
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesFree-form runtime target label supplied by the caller.
brief_idNoOptional public brief id this run is associated with.
metadataNoOptional caller-owned metadata for this run.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations are provided, so the description carries full burden. It transparently describes all side effects: creates state-only record, allocates paths, persists atomically, appends event. It also clarifies that it does not execute work.

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 well-structured with clear sections, no unnecessary words, and an illustrative example. Every sentence adds value.

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?

Given the tool has an output schema (implied), 3 parameters, and an output schema, the description covers purpose, usage, exclusions, and example. No significant gaps for a registration tool.

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 coverage is 100%, so the baseline is 3. The description adds value through an example showing typical usage of target and brief_id, and the metadata parameter is mentioned. It provides context beyond the schema descriptions.

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 it registers a public transport run with specific actions (state-only record, artifact paths, atomic persistence). It distinguishes from siblings by explicitly saying not to use for work execution or lightweight logging, and points to post_event as an alternative.

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 provides explicit 'When to use' and 'When NOT to use' sections, including alternative tools. This gives clear guidance on appropriate scenarios.

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