Skip to main content
Glama

Havidíjas szolgáltatások

list_online_services
Read-onlyIdempotent

A Kódvéna jelenleg elérhető havidíjas online szolgáltatásai (foglaló, ügyfélszolgálat, ingatlanportál, piactér stb.) címmel, linkkel és rövid leírással.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond them by stating what each entry contains — title, link and short description — which effectively communicates the return shape in the absence of an output schema. It does not mention item counts, ordering or whether unavailable services are excluded, which keeps it below 5.

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

Conciseness5/5

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

A single front-loaded sentence with no filler: scope first, then the enumerable examples, then the fields returned. Nothing is repeated and nothing needs trimming.

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 zero-parameter read-only catalog tool with no output schema, the definition supplies what an agent needs: the scope, the domain examples, and the fields each result carries. Minor omissions — no indication of result volume, ordering, or how 'currently available' is determined — are the only gaps.

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 takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The schema is an empty object and the description correctly refrains from inventing input options.

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 concrete resource and its scope: Kódvéna's currently available monthly-fee online services, with examples (booking, customer support, real estate portal, marketplace) and the fields returned. An agent can tell this is a catalog listing of paid subscription services rather than a generic list, and the 'havidíjas' qualifier implicitly separates it from list_free_tools. It stops short of naming a sibling explicitly, so it is clear but not maximally differentiated.

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 name and the 'jelenleg elérhető' (currently available) qualifier; there is no explicit when-to-use statement, no when-not, and no pointer to list_free_tools or list_pages as alternatives. An agent can infer the intent from the domain wording, but must reason about which list tool to pick.

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