Skip to main content
Glama
Sign In

AgentCompute

by io.github.Ockram4444
OverviewDiscussionsAdmin

Read a Studio task status

get_studio_job
Read-onlyIdempotent

Read your own chat, image, agent, catalog or coordinated-analysis job. Includes partial text while running, final text or image availability, GPU runtime and server timings. Wait poll_after_seconds between checks; stop on succeeded, failed or expired. Does not create or retry work.

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": {
      "job_id": "<job_id>"
    },
    "name": "get_studio_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesExact owned job identifier returned by submission; preserve it for polling and retrieval.
access_tokenNoAccount API credential from My account; omit when Bearer authorization is configured. Never include it in prompts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / access_token / description
      Added value: +"Account API credential from My account; omit when Bearer authorization is configured. Never include it in prompts."
    • addedInput schema / properties / job_id / description
      Added value: +"Exact owned job identifier returned by submission; preserve it for polling and retrieval."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that partial text is returned while running, final text or image availability, GPU runtime and server timings. It also names the terminal statuses and the polling cadence, which are essential behavioral details not captured by readOnly/idempotent hints.

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?

Three tight sentences, front-loaded with the resource and job types, followed by return behavior and polling guidance. No sentence is redundant.

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?

Although no output schema exists, the description explains what is returned at each stage (partial text, final text or image availability, GPU runtime, server timings). For a read-only polling tool with complete schema coverage, this is sufficient for correct invocation.

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

Parameters3/5

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

Schema coverage is 100%, so job_id and access_token are already fully documented in the schema. The description adds polling semantics but no additional meaning about parameter formats beyond what the schema provides, making the baseline 3 appropriate.

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 opens with a specific verb and resource: read your own chat, image, agent, catalog or coordinated-analysis job. It clearly distinguishes this read/poll operation from submission siblings by stating it does not create or retry work.

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?

It explicitly instructs the agent to wait poll_after_seconds between checks and to stop on succeeded, failed or expired. It also states the negative case: this tool does not create or retry work.

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

All AgentCompute 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