Skip to main content
Glama

Lepiej Widoczny – audyt WordPress/WooCommerce

Dobierz usługę do problemu

dobierz_usluge
Read-onlyIdempotent

Na podstawie opisu problemu (np. „sklep wolno działa na telefonie”, „link na Facebooku bez zdjęcia”, „Przelewy24 odrzuciło sklep”) zwraca pasujące usługi Lepiej Widoczny z ceną, czasem realizacji, zakresem i linkami do bezpłatnego przeglądu i zamówienia.

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": {
      "problem": "<problem>"
    },
    "name": "dobierz_usluge"
  }
}

Input Schema

NameRequiredDescriptionDefault
problemYesOpis problemu użytkownika własnymi słowami.

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 a safe, read-only, idempotent, closed-world operation, so the description only needs to add what those don't cover. It does: it discloses the returned payload (services with price, delivery time, scope, and links to a free review and to ordering), which tells the agent this is a recommendation-plus-upsell surface. It omits what happens when nothing matches or how many services come back.

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?

One sentence, front-loaded with the input examples before the outcome, and nothing is filler. The three inline examples add length but genuinely anchor the expected input, so they earn their place.

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 tool with no output schema, the definition covers input shape and output contents in a single sentence. Remaining gaps (no-match behavior, result count, whether matching is keyword- or model-based) are minor but real given the free-text input.

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

Parameters4/5

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

Schema coverage is 100% and the single parameter is already documented as the user's own words. The description still compensates usefully by giving three concrete sample problem statements, which clarifies the expected granularity and phrasing of the input beyond the schema's generic wording.

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 transformation: it takes a free-text problem description and returns matching 'Lepiej Widoczny' services with price, timeline, scope and ordering links. That is far more than a restatement of the name. It stops short of explicitly contrasting itself with siblings like cennik or audyt_strony, so the agent must infer that this is the routing/recommendation tool rather than a price list or audit.

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 through the three example problem phrasings, which show the kind of input expected but not when to prefer this over cennik (pricing) or audyt_strony (site audit). There are no exclusions or prerequisites. An agent can guess the trigger condition, but the definition does not route it explicitly.

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