Skip to main content
Glama

NETIM: agencja marketingu internetowego

Szukaj na netim.pl

szukaj
Read-only

Wyszukuje wpisy i podstrony netim.pl po frazie. Zwraca do 5 wyników z tytułem, adresem i fragmentem.

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": {
      "fraza": "<fraza>"
    },
    "name": "szukaj"
  }
}

Input Schema

NameRequiredDescriptionDefault
frazaYesSzukana fraza, np. pozycjonowanie sklepu

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral facts: results are capped at 5 and each carries a title, address, and snippet, which sets expectations about result volume. It does not say what happens with zero matches or how results are ranked.

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 compact sentences with zero filler, and the core operation is front-loaded before the return-value detail. Nothing could be removed without losing information.

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 one-parameter read-only search with no output schema, the description is nearly complete: it discloses the result cap and the fields returned, standing in for the missing output schema. Only edge-case behavior (no results, ranking, exact vs partial matching) is left open.

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 100% and the single parameter already documents itself with the same example phrase. "po frazie" restates the parameter without adding syntax, matching behavior, or indexing constraints, so the baseline 3 applies.

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?

"Wyszukuje wpisy i podstrony netim.pl po frazie" gives a specific verb (search) plus a precise resource scope (posts and subpages of netim.pl). It is clearly distinguishable from the sibling tools kontakt (contact) and lista_uslug (service listing), though it never contrasts itself with them 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?

Usage is only implied: the phrase-based search framing suggests it is the tool for finding site content, but there is no statement of when to prefer it over the siblings, no preconditions, and no exclusions. For a single-purpose lookup tool this is minimally adequate rather than helpful.

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