Skip to main content
Glama

Singing Pet

Get a pet song

get_pet_song
Read-onlyIdempotent

The state of a song made with create_pet_song: its status, lyrics, preview links, the checkout link once the preview is ready, and the HD video and gift page once paid and rendered. Poll it about every 15 seconds while the status is previewing, and every 30 seconds while paid or rendering. Follow next_step.

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": {
      "song_id": "<song_id>"
    },
    "name": "get_pet_song"
  }
}

Input Schema

NameRequiredDescriptionDefault
song_idYesThe id create_pet_song returned.

Output Schema

NameRequiredDescriptionDefault
idYes
tierYes
priceYes
styleYes
titleYes
voiceYes
lyricsYes
objectYes
statusYesdraft, previewing, preview_ready, preview_failed, paid, rendering, ready, render_failed or refunded.
paymentYes
speciesYes
languageYes
occasionYes
pet_nameYes
poll_urlYes
ready_atYes
next_stepYesWhat to do next, for the assistant.
photo_urlYes
video_urlYesThe HD MP4, once ready.
created_atYes
duration_sYes
manage_urlYes
checkout_urlYesWhere the person pays for the HD video. Present once the preview is ready.
credits_costYes
relationshipYes
gift_page_urlYesA page to send the recipient, once ready.
thumbnail_urlYes
recipient_nameYes
credits_refundedYes
preview_clip_urlYesA 5 second watermarked clip of the pet singing.
preview_audio_urlYesThe whole song as an MP3, free to play.
video_vertical_urlYes
checkout_expires_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: status-dependent return fields and polling cadence. It does not discuss authentication or rate-limit failures, but the polling intervals are a meaningful addition.

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?

The description is two tight sentences with the resource state front-loaded and polling guidance following immediately. Every clause adds useful information without repetition or filler.

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?

An output schema exists, so return values need not be fully explained, but the description still summarizes the key state fields. It also covers polling behavior and next_step, making it complete for an agent to call and re-poll this tool correctly.

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%, and the single song_id parameter is already documented as the id returned by create_pet_song. The description reinforces that relationship but does not add syntax or format details beyond the schema, so baseline 3 is 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 states a specific resource and scope: the state of a song made with create_pet_song, including status, lyrics, preview links, checkout link, HD video, and gift page. It clearly distinguishes this retrieval tool from the creation sibling by describing the returned state rather than the creation action.

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 explicit polling guidance: about every 15 seconds while previewing and every 30 seconds while paid or rendering, plus 'Follow next_step.' This is clear usage context, though it does not explicitly exclude alternatives such as get_video_status.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources