Control Plane

Get Workload Logs

get_workload_logs

Read-onlyIdempotent

Query workload logs from a GVC. Provide structured params (gvc, workload, container, location, filter) OR a raw LogQL query — a raw query REPLACES the structured params, so it must embed ALL labels itself. Available labels: gvc, workload, container, location, provider, replica, stream — replica and stream are only reachable via a raw query. filter is a literal substring match (|=), not regex; for regex use a raw query with |~. Cron run logs: scope a raw query by the replica from list_deployments jobExecutions.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	Absolute end time (exclusive, ISO 8601).
`gvc`	No	GVC name. Required unless raw `query` is provided.
`org`	No	Organization slug.
`from`	No	Absolute start time (inclusive, ISO 8601). Overrides `since`. Must be earlier than `to`.
`limit`	No	Maximum log entries to return (default: 30, max: 999).
`order`	No	Sort order (default: "oldest_first").
`query`	No	Raw LogQL query. REPLACES the structured params entirely, so it must embed ALL labels itself (gvc, workload, location, …) — required for the replica/stream labels, which have no structured param. Not sanitized — use structured params when possible.
`since`	No	Lookback window as relative duration (default: "1h"). Examples: "30m", "2h", "1d".
`filter`	No	Literal substring filter (LogQL `\|=`) — only return log lines containing this exact text. NOT a regex; for regex matching use a raw `query` with `\|~`.
`location`	No	Location to filter logs for (e.g., "aws-us-east-1").
`workload`	No	Workload name to filter logs for.
`container`	No	Container name to filter logs for (e.g., "main", "_accesslog").

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`data`	No	The full result. Read this, not only the summary.
`details`	No
`summary`	Yes
`nextSteps`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 schema fields changedSep 30, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / container / minLength
```
Removed value: -1
```
- removedInput schema / properties / from / maxLength
```
Removed value: -40
```
- removedInput schema / properties / gvc / minLength
```
Removed value: -1
```
- removedInput schema / properties / location / minLength
```
Removed value: -1
```
- changedInput schema / properties / org / description
```
Previous value: -"Organization slug (lowercase kebab-case). NEVER guess — if the user has not named one, ask. On org-not-found, stop and ask; do not retry variants."New value: +"Organization slug."
```
- removedInput schema / properties / org / maxLength
```
Removed value: -63
```
- removedInput schema / properties / org / minLength
```
Removed value: -1
```
- removedInput schema / properties / org / pattern
```
Removed value: -"^[a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?$"
```
- removedInput schema / properties / query / maxLength
```
Removed value: -500
```
- removedInput schema / properties / query / minLength
```
Removed value: -1
```
- removedInput schema / properties / since / maxLength
```
Removed value: -20
```
- removedInput schema / properties / to / maxLength
```
Removed value: -40
```
- removedInput schema / properties / workload / minLength
```
Removed value: -1
```
- removedInput schema / required
```
Removed value: -[
-  "org"
-]
```
- removedOutput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedOutput schema / additionalProperties
```
Removed value: -false
```
- changedOutput schema / properties / data / description
```
Previous value: -"The full machine-readable result — list rows, the resource object, query results. Read THIS, not just the summary."New value: +"The full result. Read this, not only the summary."
```
- addedOutput schema / properties / details
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / nextSteps / description
```
Removed value: -"Recommended follow-up actions for this task, in order."
```
- removedOutput schema / properties / ok / description
```
Removed value: -"Whether the call succeeded."
```
- removedOutput schema / properties / summary / description
```
Removed value: -"One-line summary of the result."
```
First observedJun 28, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive behavior, but the description adds material context: the raw query path is 'not sanitized' and silently overrides all structured params, and replica/stream labels are unreachable otherwise. It stops short of noting permissions or result-size behavior, so not a full 5.

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 verb and the OR/REPLACES distinction, and every clause carries information. It is dense and somewhat run-on in the back half (label list plus cron guidance in one breath), but there is little wasted text.

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 12-param, zero-required tool with a full output schema, the description covers the decision logic (structured vs raw), the label surface, the filter semantics and the cron edge case. Nothing needed to invoke it correctly is missing.

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

Parameters5/5

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

Schema coverage is already 100%, yet the description adds semantics the schema lacks: the full set of available labels (gvc, workload, container, location, provider, replica, stream), which ones are only reachable via raw query, and the exact LogQL operator behind `filter` (|= vs |~). This meaningfully extends the parameter contract.

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?

States a specific verb (query) plus resource (workload logs) scoped to a GVC, which cleanly distinguishes it from query_metrics, query_traces and get_workload_events. An agent can identify the tool's function without opening the schema.

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?

Explicitly presents the two mutually exclusive modes (structured params OR raw LogQL query), states that a raw query REPLACES structured params, and names the fallback for regex (raw query with |~) versus literal filter. It even routes a specific scenario (cron run logs) to the `replica` value from list_deployments.

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

All Control Plane 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.