Skip to main content
Glama
Sign In

Treza

by io.github.treza-labs
OverviewDiscussionsAdmin

Get timeline render

get_project_render
Read-onlyIdempotent

Where a render_project render is: status "pending" or "running" (call again after pollAfterSec), "success" with the finished file's url, or "error". Omit jobId for the project's last finished render.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "get_project_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdNoThe jobId render_project returned.
projectIdYesFrom list_projects or open_run_in_timeline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, and the description adds genuinely new context: the polling loop semantics and the exact status vocabulary including the url on success and error state. It does not elaborate on error payloads or behavior for an invalid/expired jobId, which keeps it below 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?

A single dense sentence with no filler, and the status enumeration is ordered from actionable (poll again) to terminal (success/error). The 'Where a ... is:' opener is awkward and slightly delays the understandable core, otherwise it is tight.

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?

For a two-parameter read tool with no output schema, the description covers every meaningful return state and the key polling instruction, which is exactly what an agent needs to drive the call loop. Minor gaps remain around non-existent or expired jobIds and what 'error' actually contains.

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 baseline would be 3, but the description adds real meaning the schema lacks: jobId is effectively optional in practice, and omitting it returns the project's last finished render. It also introduces pollAfterSec as a response-driven pacing hint.

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?

The description ties the tool directly to the render_project sibling and frames it as reading a render's status, with the three possible states spelled out. The opening phrasing 'Where a render_project render is' is slightly elliptical rather than a clean verb+resource statement, but an agent can still tell it is a status-poll for a specific render job.

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?

It gives concrete call conditions: re-call after pollAfterSec while pending/running, and omit jobId to get the project's last finished render. It does not explicitly state when not to use it (e.g., use get_project for project metadata), so it falls short of full alternative routing.

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

All Treza toolsInspect
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