Skip to main content
Glama

Upravio public knowledge

Pretraži javno znanje o Upraviju

search_knowledge
Read-onlyIdempotent

Pretraga ugovora, obveza, AI obrade, pohrane i uvođenja na hrvatskom ili po engleskim ključnim riječima. Vraća javne izvore i granice; nije generativni odgovor.

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_knowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 a closed-world scope, so safety is covered. The description adds genuinely new behavioral context: it returns public sources and stated boundaries rather than a synthesized answer, which sets the agent's expectation about result shape and trust level. It still does not describe ranking, result count behavior, or what an empty result means.

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 dense sentences, front-loaded with the searchable domain and followed by the output expectation. No filler, no restatement of the tool name, and the most decision-relevant clause (not a generative answer) is placed where it will be read.

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 two-parameter read-only search tool with annotations and no output schema, the description covers purpose, input language and output character well. The remaining gap is the unexplained limit parameter and the absence of any note on result ordering or pagination, which is minor at this complexity.

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 must carry parameter meaning on its own. It does clarify the query parameter by stating that Croatian terms or English keywords are acceptable, which is real added value the schema does not convey. The limit parameter (default 5, max 9) is never mentioned, leaving half the parameters undocumented.

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 ("Pretraga" / search) and enumerates the resources covered: contracts, obligations, AI processing, storage and implementation. It also states the input language condition (Croatian or English keywords) and the output nature (public sources and boundaries, not a generative answer), which separates it from a generic answer-generating tool. It does not distinguish itself from the sibling get_knowledge, 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 agent learns the tool is a source search and explicitly "nije generativni odgovor", which hints at when to prefer it over a generation path. There is no explicit when-to-use or when-not guidance, and no reference to alternatives such as get_knowledge or list_capabilities.

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