Skip to main content
Glama

Top scorers

top_scorers
Read-onlyIdempotent

The 2026/27 Premier League top scorers (league goals only), with club and appearances. Default 10, at most 20.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many players, 1 to 20 (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description contributes the scope constraint (league goals only) and the returned fields (club, appearances), which is genuine added context, but it says nothing about ordering (presumably descending by goals), tie-breaking, or whether the list is truncated when fewer than `limit` players qualify. With annotations carrying most of the burden, a 3 is fair.

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?

One efficient sentence that front-loads the resource and scope before the size constraint. The only waste is repeating the default/maximum values already present in the schema.

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 single-optional-parameter read tool with no output schema, the definition covers what data is returned (club, appearances) and the metric definition (league goals only), which is what an agent needs to call it correctly. Missing only ordering semantics, which is a minor gap given the tool's simplicity.

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% and the single `limit` parameter is already documented with bounds and a default of 10. The description simply restates 'Default 10, at most 20' rather than adding meaning such as behavior when limit exceeds available players. Baseline 3 applies when the schema does the heavy lifting.

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

Purpose4/5

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

The description names a precise resource and scope: '2026/27 Premier League top scorers (league goals only), with club and appearances.' The 'league goals only' qualifier pre-empts the obvious ambiguity of cup/European goals, so an agent knows exactly which dataset this is. It stops short of contrasting with a sibling like table or results, which is why it's a 4 rather than a 5.

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?

Usage is only implied by the resource itself — a request for scoring leaders maps naturally here. There is no explicit when-to-use framing, no statement of what this is not for, and no pointer to an alternative (e.g. table for standings). Adequate but leaves routing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources