Skip to main content
Glama
Sign In

AgentCompute

by io.github.Ockram4444
OverviewDiscussionsAdmin

Retrieve your generated PNG

get_studio_image
Read-onlyIdempotent

Return the completed image as an MCP image content block. Requires the same token/identity that submitted the job. Images expire after 24 hours from submission; download before expiry.

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_image"
  }
}

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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds genuinely new behavior: the return is an image content block, retrieval is bound to the submitting identity, and results expire 24 hours after submission. It does not describe what happens if the job is incomplete or how errors surface.

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?

Two tight sentences, zero filler, with the primary action and return type front-loaded before the prerequisites. Every clause contributes a distinct fact (return format, auth binding, expiry).

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?

No output schema exists, and the description appropriately names the return type; auth and retention constraints are also covered. The remaining gap is failure-mode behavior when the job is not yet complete or the token does not match, which an agent would benefit from knowing.

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 description coverage is 100%, with job_id format and access_token usage already fully documented, so the schema carries most of the burden. The description adds only the ownership/identity constraint that the credential must match the one that submitted the job, which is useful but marginal at this coverage level.

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?

States a specific verb and resource ("Return the completed image") plus the concrete return form ("MCP image content block"), which distinguishes it from status-oriented siblings like get_studio_job. It does not name a sibling explicitly, so the differentiation is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a prerequisite ("Requires the same token/identity that submitted the job") and a deadline ("download before expiry"), which implies the tool is used after a job completes. It never says how to know the job is ready or that get_studio_job should be polled first, so the when-to-use routing is left to inference.

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