Skip to main content
Glama

Lepiej Widoczny – audyt WordPress/WooCommerce

Szukaj w poradnikach

szukaj_poradnikow
Read-onlyIdempotent

Wyszukuje w ponad 50 poradnikach Lepiej Widoczny o szybkości stron, danych dla Google i AI, WooCommerce, PHP, Black Friday, Omnibusie i utrzymaniu WordPressa. Zwraca tytuły, adresy i krótkie odpowiedzi.

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": {
      "zapytanie": "<zapytanie>"
    },
    "name": "szukaj_poradnikow"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
zapytanieYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 the safety profile is covered. The description adds genuine value by disclosing the return shape ('tytuły, adresy i krótkie odpowiedzi'), warning the agent that results are excerpts, not full content. It does not mention result counts, the effect of the limit parameter, or any pagination/empty-result behavior.

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 front-loaded sentences with no filler; the search scope comes first and the return format second. The topic enumeration is long but earns its place by signalling the content domain the query should target.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only two-parameter search with no output schema, the description does explain the returned fields, which is the important missing piece elsewhere. However, with 0% schema coverage it leaves the query parameter and the result limit completely unexplained, which is a real gap for an agent composing a call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters, so the description must carry the burden and it does not: neither 'zapytanie' nor 'limit' is mentioned. Nothing explains what the query accepts (keywords, phrase, Polish/English) or that limit caps the number of returned guides at 1-10.

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 ('Wyszukuje') plus the resource ('w ponad 50 poradnikach Lepiej Widoczny') and enumerates the covered topic areas, so an agent knows exactly what corpus is searched. It stops short of naming the natural alternative (pobierz_poradnik for full guide content), so sibling differentiation is only implied rather than stated.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The agent can infer it is a discovery tool that returns short answers rather than full articles, but the choice between this and pobierze_poradnik or search is left entirely 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