Skip to main content
Glama

Lepiej Widoczny – audyt WordPress/WooCommerce

Plan poprawy strony

plan_poprawy
Read-onlyIdempotent

Uporządkowany plan poprawy na podstawie audytu: najważniejsze problemy, zadania do zrobienia samodzielnie (z szacowanym czasem i poradnikiem) oraz usługi Lepiej Widoczny, które je rozwiązują (cena, czas, link do 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": {
      "url": "<url>"
    },
    "name": "plan_poprawy"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAdres strony lub sklepu, np. twoj-sklep.pl

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description usefully discloses that the output is partly commercial (service offers with prices and order links), which is real context beyond the annotations. It does not say whether it fetches the URL live, whether a prior audit is required, or how long generation takes.

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?

A single front-loaded sentence that names the deliverable first and then unpacks its parts; every clause carries information. It is dense but not padded, though the nested parenthetical lists make it slightly harder to scan.

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?

With no output schema, the description appropriately describes what comes back (problems, tasks with estimates, service offers with price and order link), which is what an agent needs to decide relevance. The remaining gap — whether it performs its own site fetch versus consuming an existing audit — is modest for a read-only, single-parameter tool.

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?

Only one parameter with 100% schema coverage and an example format, so the schema already carries the meaning. The description adds nothing parameter-specific, which is fine at baseline for a single well-documented input.

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 deliverable — an ordered improvement plan derived from an audit — and enumerates its three components (key problems, DIY tasks with time estimate and guide, matching Lepiej Widoczny services with price/time/order link). This clearly separates it from audyt_strony (the diagnosis itself), though no sibling is named 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 'na podstawie audytu' suggests it belongs after/wit an audit, and the mix of DIY tasks plus purchasable services hints at post-diagnosis next steps. There is no explicit statement of when to pick this over audyt_strony, cennik, or dobierz_usluge.

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