Skip to main content
Glama
Sign In
rankedtoday-mcp

rankedtoday-mcp

by RyanKramer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rankedtoday_tools

Estimate League of Legends MMR, project climb, compute KDA, and assess cognitive readiness using sleep and reaction time data.

Instructions

Free tools and cognitive tests on the web.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states what the tool 'is' (free tools and tests) rather than what it does, any side effects, or limitations. There is no transparency about operations, data handling, or interactions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, so it is concise in length. However it is under-specified to the point of being unhelpful, and the sole sentence does not meaningfully earn its place beyond stating an obvious category.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema (which is not described), the tool has no parameter schema and no behavioral context. The description fails to explain what the tool actually does, what results it returns, or how it integrates with sibling tools. For a zero-parameter tool, the complete lack of specificity leaves the agent without enough information to invoke it correctly or interpret its output.

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?

The tool has zero parameters, so the baseline for this dimension is 4. The description adds no parameter-level detail, but since there are no parameters to document, this is acceptable.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Free tools and cognitive tests on the web' is vague and does not specify a concrete action or resource. It reads as a category label rather than a tool purpose, and does not differentiate from sibling tools like kda or climb_calculator.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description gives no context for selection, and the tool's relationship to its siblings is entirely unexplained.

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