Skip to main content
Glama

Trending sounds

get_trending_sounds
Read-only

What people are actually pressing on DankMachine right now.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_trending_sounds"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
windowNo24h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds essentially nothing beyond that: no mention of result ordering, whether the list is ranked, how the time window affects results, or the 25-item cap. Worse, "right now" implies a live feed while the schema defaults to a 24h window, creating a mild behavioural mismatch.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but brevity here is under-specification rather than efficiency. The single fragment is not front-loaded with any actionable information and contains filler ('actually').

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With two parameters, one unenumerated vocabulary, no output schema, and only minimal annotations, the description needed to explain what is returned, how it is ordered, and what each window value means. It does none of these, so an agent cannot confidently call the tool or interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters, so the description carries the full burden and fails. Neither the 'limit' cap nor the 'window' enum (especially what 'rising' means versus '1h'/'24h'/'7d') is explained anywhere, leaving an agent to guess the semantics of the core control.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The line "What people are actually pressing on DankMachine right now" gestures at popularity-ranked sounds but never names the resource explicitly or states a verb like 'list' or 'rank'. It reads as a casual restatement of the title rather than a distinguishable definition, and it doesn't separate itself from siblings such as search_sounds or get_random_sound.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this over search_sounds, get_random_sound, or list_categories, nor any exclusion. The phrase "right now" weakly implies a real-time trending use case, but it's ambiguous enough to mislead given the tool accepts 7d windows.

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.