Skip to main content
Glama

Live Card

by app.openkrill
OverviewDiscussionsAdmin

Check a Live Card render

live_card_status
Read-onlyIdempotent

Use this when a Live Card render was queued and you have its job_id. Call it again while status is queued or rendering. When status is ready, downloads holds four links (jpeg, mov, mp4, gif) and content_identifier is the Apple id shared by the JPEG and the MOV. Give the user every link and say they expire at expires_at (24 hours). The JPEG and MOV are the Live Photo pair. The MP4 and GIF play elsewhere. status failed includes error_code. status expired means the files were deleted. A wrong job_id is not_found. It does not start a render.

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job_id returned by render_live_card.

Output Schema

NameRequiredDescriptionDefault
as_ofYes
job_idYes
sourceYes
statusYes
messageYes
downloadsNo
error_codeNo
expires_atNo
content_identifierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "job_id": "eb10d3e39ceb8ecd10f5f39d0ec757cf"
+  }
+]
  2. Changed1 schema field changed
    • removedOutput schema / properties / note_from_openkrill
      Removed value: -{
-  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
-  "type": "string"
-}
  3. Changed1 schema field changed
    • addedOutput schema / properties / note_from_openkrill
      Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Far beyond the annotations, it enumerates the status machine (queued/rendering/ready/failed/expired), what each terminal state carries (four download links, error_code, deleted files, not_found for a bad id), the 24-hour expiry at expires_at, and the JPEG/MOV Live Photo pairing. This is exactly the operational context an agent needs for a polling tool.

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 trigger condition and polling instruction, then the result interpretation. Nearly every sentence carries distinct information, though the back half reads as a dense run of status facts rather than a clearly partitioned list.

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?

A one-parameter read tool with an output schema and full annotations; the description covers polling cadence, every status branch, link expiry, and the render/no-render boundary. Nothing an agent needs to call or interpret it correctly is missing.

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% and already documents job_id's origin and hex pattern, so the description only needs to add meaning; it does so by explaining the failure mode for a wrong job_id (not_found). That is useful but narrow, hence not a 5.

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 and resource ('check a Live Card render' status) and explicitly carves out scope with 'It does not start a render', which points the agent to render_live_card. Unambiguously separable from its siblings.

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?

Gives an explicit trigger ('when a Live Card render was queued and you have its job_id') and an explicit polling loop ('Call it again while status is queued or rendering'), plus an exclusion for the render-starting sibling. Nothing is left to inference about when to call it versus render_live_card.

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

All Live Card 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