Skip to main content
Glama

Týdenní přehled sledovaného místa

tydenni_prehled
Read-onlyIdempotent

Vrátí oznámení za jeden týden pro obec, adresu nebo komunitu, kterou uživatel sleduje (stejný výběr jako v týdenním e-mailu). Bez parametru tyden platí aktuální týden.

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": {
      "typ": "<typ>",
      "id": "<id>"
    },
    "name": "tydenni_prehled"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifikátor z nástroje moje_sledovane.
typYesDruh sledovaného místa.
tydenNoLibovolné datum (RRRR-MM-DD) v požadovaném týdnu; týden začíná pondělím.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/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 safety is covered structurally. The description's one added behavioral fact is the default to the current week when tyden is omitted; it says nothing about volume, pagination or what an 'oznámení' record contains.

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?

One tightly written sentence plus a short default-behavior clause; the scope and the source of the selection are front-loaded and nothing is redundant.

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 read-only, idempotent, fully documented 3-parameter tool with no output schema, the definition covers what the agent needs to call it. The one gap is that it does not describe the shape of a returned oznámení, which the missing output schema would otherwise require.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuinely non-schema information: omitting tyden returns the current week, and the result set mirrors the weekly e-mail selection. That meaningfully clarifies the optional parameter's behavior.

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 gives a specific verb and resource ('Vrátí oznámení') scoped to a week and to a watched place of type obec/adresa/komunita, which cleanly separates it from sibling tools like zasedani_obce or smlouvy_obce. It does not explicitly name a sibling it is not, so it falls short of 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 implied rather than stated: the tool applies to a place the user already follows, and the schema notes the id comes from moje_sledovane, which hints at the prerequisite flow. There is no explicit when-not-to-use guidance or named alternative, so the agent must infer the routing.

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