Skip to main content
Glama
Sign In

Achriom

by com.achriom.mcp
OverviewDiscussionsAdmin

Get popularity charts

get_charts
Read-onlyIdempotent

Popularity charts: the most popular movies, shows, anime, books, games, albums or manga this month, this year, of the past 5 years, of the decade or of all time, plus the most popular movie and book series, directors and authors. Counted from TMDB ratings, AniList members, IGDB ratings, Open Library reading logs and Apple Music's chart, or by how many Achriom libraries keep a title; these are not sales figures. Titles already in their library are marked. Use it when they ask what is popular, a best-of or a top list, or what is big right now.

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": {
      "media_type": "<media_type>"
    },
    "name": "get_charts"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNotitles (default); series (movie, book); creators (movie directors, book authors). Series and creators are all time only.
limitNoHow many to list (default 20, max 50)
sourceNoworld (the outside source, default) or here (what the most Achriom libraries keep)
windowNomonth (the last 30 days, or right now), year, 5y (past 5 years), decade, or all (default)
media_typeYesWhich kind of chart

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the read-only/idempotent annotations by disclosing data provenance (TMDB ratings, AniList members, IGDB ratings, Open Library logs, Apple Music chart, or Achriom library holdings), warning that these are not sales figures, and noting that titles already in the user's library are marked. These are exactly the behavioral facts an agent needs to interpret and caveat the result correctly.

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 resource and its full scope, then the data-source caveat, then the usage trigger. The first sentence is dense but every clause carries selection signal; nothing is filler, though the enumeration of media types and windows could be trimmed since the schema repeats them.

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 five-parameter read tool with no output schema, the description conveys what comes back (ranked charts of titles/series/creators), the data behind them, and the in-library marking. It does not describe result ordering explicitly or pagination, but with only a limit parameter and no cursor, nothing essential is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds value by restating the window options in natural language and clarifying what 'world' versus 'here' means at the data level ('by how many Achriom libraries keep a title'), which gives the enum a concrete interpretation rather than a label.

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?

States a specific resource and enumerates its scope precisely: popular movies, shows, anime, books, games, albums, manga plus series, directors and authors. An agent can immediately tell this apart from sibling tools like get_by_rating, get_taste or get_recommendations, which are personalized rather than chart-based.

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?

Gives explicit trigger phrasing: 'Use it when they ask what is popular, a best-of or a top list, or what is big right now.' That covers the primary invocation intents. It stops short of naming alternatives (e.g. 'for personalized picks use get_recommendations'), so there is no explicit exclusion guidance, but the context is clear.

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

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