Grep.FM

Get chart

get_chart

Read-only

Today's top podcasts chart for a country on Apple Podcasts or Spotify, overall or for one category: each show's place, its move since the previous chart, and its Grep.FM id when the show is in the database (pass it to get_podcast, or put it into podcast_link to link the show). Spotify also has a Trending chart.

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_chart"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many places to return, 1 to 200.
`country`	No	An ISO country code such as us, gb or de, or the English name.	us
`category`	No	A chart such as Business or True Crime; leave it out for the overall chart. Apple also charts subcategories (Entrepreneurship, Investing); a name that isn't charted lists the ones that are.
`platform`	No	apple or spotify.	apple

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish a read-only, non-destructive, non-open-world profile, so the description does not need to restate safety. It adds useful behavior beyond that: each show's place, movement, database id, id reuse with get_podcast/podcast_link, and the extra Spotify Trending chart.

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?

The description is front-loaded with the core chart scope and packs return-value and id-linkage details into a single efficient sentence. It is dense but nearly all information earns its place.

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, but the description enumerates the key return values and explains how the Grep.FM id is used. Combined with complete parameter documentation and safety annotations, it gives an agent enough to call the 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%, so the schema already documents country, category, platform, and limit. The description reinforces category/overall and platform behavior, but it adds little parameter semantics beyond the schema and does not mention the limit parameter.

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?

It states a specific retrieval action and resource: today's top podcast chart by country, platform, and category/overall. It also names the returned fields and the Grep.FM id, making the chart-oriented scope distinct from sibling tools such as get_podcast.

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?

The chart-retrieval context is clear and it tells the agent to pass the returned id to get_podcast or podcast_link, but it never explicitly says when to choose this over sibling search/find tools or when not to use it.

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

All Grep.FM tools Inspect

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

Need Help?