Skip to main content
Glama

Lepiej Widoczny – audyt WordPress/WooCommerce

Search (poradniki Lepiej Widoczny)

search
Read-onlyIdempotent

Search Lepiej Widoczny guides about WordPress/WooCommerce speed, SEO, AI visibility and maintenance (Polish). Returns results with id, title, url.

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: the result shape (id, title, url) and the fact that the corpus is Polish-language — useful because no output schema exists. It says nothing about result limits, ranking, or 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the verb and corpus, followed by the return fields. Every clause carries information; there is no filler or repetition of the title.

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 single-parameter read-only search tool with rich annotations, the definition covers corpus scope, language, and return fields, which is close to sufficient. The missing pieces — differentiation from 'szukaj_poradnikow' and any note on result count or pagination — are what keep it from being complete.

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?

Only one parameter ('query') exists and its schema description coverage is 0%, so the description must carry the load. It implies the query is topical search terms over the guide corpus, which is modest added meaning, but says nothing about matching behavior, phrasing, or language expectations for the query string.

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 and resource ('Search Lepiej Widoczny guides') and bounds the corpus by topic (WordPress/WooCommerce speed, SEO, AI visibility, maintenance) and language (Polish). It is clear what the tool returns, but it never distinguishes itself from the near-duplicate sibling 'szukaj_poradnikow' or from 'fetch', so an agent cannot tell them apart from this text alone.

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 statement of when to use this tool, when not to, or which sibling to prefer. With 'szukaj_poradnikow' (literally 'search guides') present in the sibling list, this omission is material — the agent is left to guess which search entry point to call.

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