Skip to main content
Glama

Shazam top charts

music_charts
Read-only

Get the current Shazam top chart for a country or the whole world, paged. Returns video_id, title, duration and thumbnail_url for each song. Cost: 1 credit per page; a failed call costs 0.1.

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

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number.
countryNoTwo-letter ISO country code such as US, or world.world

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?

The annotations already disclose that this is a read-only, open-world operation, but the description adds important behavioral context beyond them: paging, per-page credit cost of 1, and a failed-call cost of 0.1. It also lists the returned fields, which helps the agent understand the result shape even without an output schema.

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?

It is three short sentences with no wasted wording. The purpose comes first, return fields follow, and cost is placed last, giving a clear front-loaded structure.

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?

For a simple read-only list tool with fully documented parameters, the description covers the essential purpose, paging, scoping, return fields, and cost model. The only minor gap is that it does not explain pagination limits or error behavior in more detail, but the supplied annotations and schema cover the safety and parameter basics.

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?

The schema already documents both parameters at 100% coverage, including the 1-based page number and the two-letter ISO country code or world. The description reinforces country/world scope and paging, but adds no syntax or format detail beyond what the schema provides.

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 verb and resource: get the current Shazam top chart, scoped to a country or the whole world, with paged results. This clearly distinguishes it from sibling media-search and download tools such as youtube_search and fetch_media.

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

Usage Guidelines3/5

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

It implies usage by describing the chart lookup and its country/world scope, but it does not explicitly state when to choose this over alternatives or when not to use it. The guidance is adequate but leaves routing decisions to inference.

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.