Skip to main content
Glama
Sign In
Rephonic

Rephonic

Official
by getrephonic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

chart_categories

Retrieve available chart categories and countries for Apple, Spotify, or YouTube podcasts. Use the returned slugs to fetch chart rankings.

Instructions

Get all available chart categories and countries for a platform. Use the returned slugs with the chart_rankings tool.

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": {
      "platform": "<platform>"
    },
    "name": "chart_categories"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesChart platform.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations provided, and the description lacks behavioral details such as read-only nature, rate limits, or output format. The agent cannot infer safety or constraints beyond the basic purpose.

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?

Two concise sentences: first states the action, second explains the output's use. Zero waste, front-loaded, and efficient.

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 single-parameter tool without output schema, the description provides adequate usage context. However, it could be more complete by hinting at the structure of the returned data.

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 coverage is 100% with a single parameter (platform) described minimally. The tool description adds no further semantic context about the parameter, so baseline score of 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 clearly states the tool retrieves chart categories and countries for a platform, and distinguishes it from sibling tools like list_categories and list_countries by specifying it returns slugs for use with chart_rankings.

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?

Explicitly directs the agent to use returned slugs with chart_rankings, providing clear context. However, it does not mention when not to use this tool versus alternatives like list_categories.

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

Deploy Server

Other Tools