Tier Maker List MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_editor_scopeA | Return the editor workflow and the documented limits on local processing or export. (Tier Maker List) |
| get_official_linksA | Return the canonical list of official links for Tier Maker List (website, support, docs when available). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| tell_me_about_tiermakerlist | Summarize what the site is, who it's for, and how it works. — Tier Maker List |
| review_edit_scope_tiermakerlist | Review an editing workflow without promising unsupported file mutation. — Tier Maker List |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| workbench | Public editing workflow, local-processing model, and documented safety limits. |
| faq | Short FAQ generated from public site metadata. |
| links | Canonical URLs to share with users. |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one provides editor scope and limits, the other returns official links. There is no ambiguity.
Both tools follow a consistent 'get_' verb_noun pattern, making them predictable and easy to understand.
With only 2 tools, the server is minimal but arguably appropriate if its sole scope is providing documentation. However, the server name implies broader tier list functionality, making it feel slightly under-scoped.
The server name suggests tools for creating or managing tier lists, but the actual tools only return metadata about the server itself. There are no CRUD or lifecycle operations for tier lists, which is a severe gap.