Vepathos

Get optimization result

get_optimization_result

Read-onlyIdempotent

Get the status and outcome of a route optimization by its optimization_id. While it runs, returns status and progress: tell the user the percent and the stage in one line, and wait poll_after_seconds before asking again. When complete, detail=summary returns totals and per-route metrics; detail=stops returns ordered stop_ids with arrival times (driver clock, service at earlier stops included). request shows the depot, vehicles and schedule it ran with. Completed results are kept with their plan: plan_id, and account_url, which opens it in the user's Vepathos account (sign-in required). Read-only; does not consume plan stops.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Page size. Defaults: 25 routes for summary, 200 items for stops and unassigned.
`detail`	No	summary: totals and per-route metrics. stops: ordered stops with arrival times. unassigned: ids of stops that could not be routed.	summary
`offset`	No	Pagination offset (routes or stops).
`route_id`	No	Only for detail=stops: return the stop sequence of this route only.
`optimization_id`	Yes	The optimization_id returned by optimize_routes.

Output Schema

TableJSON Schema

Name	Required	Description
`page`	No	Pagination for routes or stops.
`error`	No	Structured error when the tool call failed.
`stops`	No	Ordered visits when detail=stops (no coordinates echoed).
`detail`	No	Which slice of the result this payload carries.
`routes`	No	Per-route metrics page when detail=summary.
`status`	No	queued / running / completed / failed.
`plan_id`	No	The plan this lives in, in the user's Vepathos account (list_plans).
`request`	No	What this optimization ran with: depot, vehicles, schedule, objective, dataset. Reuse it to repeat or vary the run; confirm the depot and departure with the user first.
`summary`	No	Present when detail=summary and completed.
`progress`	No	Present while queued or running.
`expires_at`	No	When results stop being available (UTC). Absent: kept with the plan.
`history_id`	No	This run in the plan's history.
`account_url`	No	Opens the plan in the user's Vepathos account. Requires signing in; private to the account.
`optimization_id`	No	Same handle returned by optimize.
`poll_after_seconds`	No	When status is queued or running, call again after about this many seconds.
`unassigned_stop_ids`	No	Ids that could not be routed when detail=unassigned.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 25, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses progress reporting, polling cadence, detail-mode outputs, retention with plan_id/account_url, sign-in requirement, and that it does not consume plan stops. This is substantial behavioral context.

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 dense but front-loaded with the core purpose, then logically moves through polling, detail modes, retention, and read-only note. Every sentence adds operational value with no filler.

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 polling tool with 5 parameters and an output schema, the description covers status/progress, when to poll, detail semantics, retention, account access, and side-effect safety. Nothing essential is missing for correct invocation.

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%, and the description adds meaning for detail modes, defaults, and the meaning of optimization_id. The 'request shows...' clause is ambiguous and could be mistaken for an undocumented detail value, so not a perfect 5.

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 opening sentence names a specific verb ('Get'), resource ('status and outcome of a route optimization'), and key identifier ('optimization_id'), which clearly differentiates it from siblings like optimize_routes. It also immediately signals the polling/status nature of the tool.

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?

The description gives explicit operational guidance: report percent and stage in one line and wait poll_after_seconds before polling again. It does not name alternative tools or exclusion conditions, but the context makes the intended use clear.

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

All Vepathos tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?