Skip to main content
Glama

new_jackpots

Read-only

Supplies the content of one page from the page address, whether that is a game's details or a list of games.

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": {
      "url": "<url>"
    },
    "name": "new_jackpots"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage address of this website, either complete or beginning with a slash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with a safe read. Beyond that it adds almost nothing: it does not say what format the returned page content takes, how failures/404s behave, or whether the response is paginated, which matters for a fetch-by-URL tool.

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?

A single front-loaded sentence with no filler or repetition. It is efficiently sized, though the 'whether that is...' clause is slightly awkward and replaces what could have been a sharper statement of scope.

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

Completeness3/5

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

With one required parameter, full schema coverage, and annotations covering the safety profile, the definition is close to sufficient, but there is no output schema and the description does not characterize the return value (HTML vs. parsed data, error behavior). That leaves a meaningful gap for a page-fetch tool.

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% and the schema description already explains that the url may be complete or start with a slash. The description adds no extra meaning beyond what the schema provides, so the baseline 3 applies.

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

Purpose3/5

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

The description states a verb+resource ('supplies the content of one page') and gives two example cases (a game's details or a list of games), but 'content' is vague and the description never connects to the tool name 'new_jackpots' or distinguishes it from siblings like search or free_slots. An agent looking for a jackpots feed would not obviously pick this tool.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of the alternatives ('search', 'free_slots'). The only implicit signal is that this single tool covers both detail and list pages, which the agent must infer from the clause 'whether that is a game's details or a list of games.'

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