Skip to main content
Glama
Sign In

ViralMint

by net.viralmint
OverviewDiscussionsAdmin

Read a song summary

song_get
Read-only

Free; never starts an analysis. The song and, once read, a summary of its analysis (never the raw words, beats or energy). Captions on a song are always whole lines (never word sync).

Args: song_id: from song_from_library.

Returns: {ok, song_id, analyzed, audio_url, analysis?:{duration, bpm, language, sections:[{id,label,s,e}], lines:[{text,s,e}], line_count, word_count, beat_count}}

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": "song_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
song_idYesA song id from song_from_library.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only say readOnlyHint=true; the description adds real value on top: no cost, no analysis job kicked off, and content exclusions (no raw words, beats or energy; captions are always whole lines, never word sync). It stops short of covering latency or what happens for an unanalyzed song, but the side-effect profile is well disclosed.

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 most decision-relevant fact ('Free; never starts an analysis'), then Args/Returns blocks. The sentence 'The song and, once read, a summary of its analysis' is slightly convoluted, but nothing is padding.

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?

There is no output schema, so the Returns block is essential and it is supplied with concrete field names, including the optional nested analysis shape. For a single-parameter read tool with readOnlyHint set, an agent has everything needed to call it and interpret the result.

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 parameter already carries 'A song id from song_from_library' with a strict pattern; the description's Args line restates the same provenance without adding format, validation, or error semantics. Baseline 3 is correct when the schema does the work.

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+resource (read a song plus, if already analyzed, a summary of its analysis) and explicitly bounds the payload ('never the raw words, beats or energy'). It implicitly separates itself from song_analyze by declaring 'never starts an analysis', though it never names that sibling, so the differentiation is inferential rather than explicit.

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?

'Free; never starts an analysis' tells the agent both the cost profile and the key condition: this is a safe read that does not trigger work. The complementary case (use song_analyze if no analysis exists) is only implied via 'once read', not stated as an explicit alternative.

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

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