Skip to main content
Glama

online_kerdi

Read-only

Επιστρέφει ό,τι εμφανίζει μια σελίδα του ιστότοπου με βάση τη διεύθυνσή της: τα στοιχεία ενός παιχνιδιού ή τον κατάλογο με τα παιχνίδια.

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

Input Schema

NameRequiredDescriptionDefault
urlYesΣελίδα του παρόντος ιστότοπου ως πλήρης διεύθυνση ή ως τμήμα με αρχικό σύμβολο /.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/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 reinforces the closed-world scope by saying the page belongs to this site. It adds the useful detail that the response mirrors whatever the page displays (game details or catalog), but it does not say whether the return is raw HTML or structured data, nor anything about errors for non-existent pages.

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 sentence, front-loaded with the verb and elaborated after a colon so the two possible result shapes are immediately visible. No filler, though the phrasing is slightly roundabout compared with a direct 'returns the page content at url'.

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?

For a simple one-parameter read tool with full schema coverage and safety annotations, the essentials are present. The remaining gap is the return representation — no output schema exists, so the description should clarify whether page content comes back as markup or parsed fields, and it only gestures at this.

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 single url parameter is fully documented, including the path-form convention. The description only restates 'based on its address' and adds no syntax or format meaning beyond the schema, so the baseline 3 applies.

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 specific verb and resource: it returns the content a page of this site displays, given its address, and it concretely enumerates the two content shapes (a game's details or the games catalog). It does not, however, contrast itself with the sibling tools anazitisi or mixanes, so an agent must infer the boundary.

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 implied rather than stated: fetch a page by its address. There is no explicit when-to-use / when-not-to-use framing and no mention of when a search-style sibling would be preferable for finding a game rather than retrieving a known page.

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