Skip to main content
Glama
Sign In

Unraster

by ai.unraster
OverviewDiscussionsAdmin

Get a conversion

get_conversion
Read-onlyIdempotent

Check the status, progress and download links of a conversion started with convert_image. Free.

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": {
      "conversion_id": "<conversion_id>"
    },
    "name": "get_conversion"
  }
}

Input Schema

NameRequiredDescriptionDefault
conversion_idYesThe conversion_id returned by convert_image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the safe read profile (readOnly, idempotent, non-destructive, non-open-world), so the bar is lower; the description still adds value by enumerating the returned content (status, progress, download links) and a cost signal ('Free'). It does not say whether status is eventually consistent or whether polling is expected.

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?

One front-loaded sentence naming the resource and the fields inspected, plus a terse cost note. The trailing 'Free.' fragment is slightly abrupt but still informative rather than wasteful.

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 compensates by listing what comes back (status, progress, download links), which is the key information for a polling-style read tool. Missing only marginal detail such as polling cadence or terminal-state behavior.

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% and the single parameter is already documented as 'The conversion_id returned by convert_image'; the description's reference to convert_image duplicates that rather than adding format or lookup semantics. Baseline 3 is appropriate when the schema carries the meaning.

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 (check) and resource (status, progress, download links of a conversion) and ties it to the sibling that creates it ('started with convert_image'), so an agent can distinguish it from convert_image and quote_conversion without opening schemas.

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 phrase 'started with convert_image' establishes the prerequisite and sequencing (call this after a conversion is created), which is clear usage context. It stops short of explicit when-not guidance or mentioning quote_conversion as an alternative path.

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

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