Skip to main content
Glama

Rybárstvo.sk

Bed model of a reservoir or river

get_bed_model
Read-onlyIdempotent

Summary of the portal's 3D bed model of a reservoir, lake or river section: maximum and mean depth, water volume, surface area, water level, where the depth comes from (pre-flooding maps, literature, angling rules or an estimate), sources and notes. It is a model, not a survey: not for navigation or diving.

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": {
      "water_id": "<water_id>"
    },
    "name": "get_bed_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
water_idYesPage id of the water (from search_site or waters_near).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the epistemic caveat that values are modelled, with depth derived from pre-flooding maps, literature, angling rules or estimates. That provenance disclosure is genuinely useful for deciding how far to trust the numbers. The one omission is the behavior when no bed model exists for a given water.

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?

Two sentences, front-loaded with the verb-and-resource statement, followed by a compact field list and a closing caveat. Every clause carries information and nothing is repeated from the annotations or 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?

There is no output schema, so the field enumeration in the description usefully stands in for one, and the single required parameter is fully documented in the schema. A note on the no-model case and how to obtain a valid water_id would make it airtight, but for a one-parameter read tool this is close to complete.

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 itself already explains that water_id is the page id obtained from search_site or waters_near, so the description does not need to re-document it. It adds no additional meaning about the identifier, which is the correct baseline when the schema does the work.

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

Purpose5/5

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

States a specific resource (the portal's 3D bed model of a reservoir, lake or river section) and enumerates exactly what is returned: max/mean depth, volume, surface area, water level, depth provenance, sources and notes. That enumeration cleanly separates it from generic siblings like get_water and get_water_conditions, which an agent can distinguish without opening either schema.

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

Usage Guidelines4/5

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

Gives clear context for use (a bathymetric summary rather than an actual survey) and an explicit exclusion: 'not for navigation or diving'. It stops short of naming when to prefer get_water or get_water_conditions, so the agent must infer the routing between siblings, but the framing of what the data is and is not suitable for is unusually concrete.

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