Skip to main content
Glama

Hypotéka Online

Vyhledat články o hypotékách

search_articles
Read-onlyIdempotent

Find Czech mortgage guides by keyword, with dates, summaries and URLs for citations. Use short Czech search phrases.

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": {
      "query": "<query>"
    },
    "name": "search_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world scope, so the safety profile is covered. The description adds a useful behavioral note that results include dates, summaries, and URLs suited to citations, but says nothing about result ordering, empty-result behavior, or pagination with the limit parameter.

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?

Two tight sentences, with the core function front-loaded and the query constraint placed second where it is relevant. Nothing is redundant, though the citation-payload detail is packed into the same sentence as the core purpose.

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?

With no output schema, the description helpfully names the returned fields, and the tool is simple enough (one required param) that little more is needed. The remaining gap is the undocumented limit parameter and no guidance on choosing search versus get_article.

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 description coverage is 0%, so the description carries the burden. It explains the query parameter as a keyword phrase with a Czech-language, short-phrase constraint, but gives no meaning for 'limit' beyond the schema's numeric bounds, leaving half the parameters unexplained.

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 states a specific verb and resource ('Find Czech mortgage guides by keyword') and adds scope detail (Czech, mortgage-specific) that the name alone lacks. It also indicates the return payload, which implicitly distinguishes it from the sibling get_article, but never names an alternative explicitly.

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?

'Use short Czech search phrases' gives concrete query-construction guidance, which is real usage advice. However, there is no statement of when to use this search versus get_article, nor any exclusion or prerequisite, so routing is left to inference.

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