Skip to main content
Glama

Lepiej Widoczny – audyt WordPress/WooCommerce

Link do bezpłatnego przeglądu lub zamówienia

link_do_dzialania
Read-onlyIdempotent

Tworzy link, który użytkownik otwiera sam: bezpłatny przegląd z wypełnionym adresem i problemem (typ=przeglad) albo koszyk z wybraną usługą (typ=zamowienie). Zgody i zamówienie potwierdza zawsze człowiek.

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": {
      "typ": "<typ>"
    },
    "name": "link_do_dzialania"
  }
}

Input Schema

NameRequiredDescriptionDefault
typYes
urlNoAdres strony użytkownika (dla przeglądu).
uslugaNoSlug usługi z cennika (dla zamówienia), np. szybsza-strona.
problemNoKlucz problemu (dla przeglądu).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real value on top: it clarifies that the link is opened by the user themselves (nothing is sent or executed by the tool) and that consent and order confirmation always involve a human. It stops short of saying a link string is returned and whether links expire.

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 sentences, no filler, and the core constraint (the user opens the link themselves) is front-loaded in the relative clause before the two variants. Nothing is repeated from the schema or annotations.

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 low-complexity, read-only link-builder with no output schema, the description covers both modes and the human-in-the-loop boundary, which is what an agent needs to call it correctly. Only the shape of the result (does it return a URL string?) is left implicit, a minor gap given the tool's simplicity.

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 75% and both enums are self-documenting, so the schema already does most of the work. The description still adds meaning by tying each typ value to its purpose and to the parameters that matter for it (address and problem key for a review; service slug for an order), which exceeds a bare restatement of the schema.

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 ("Tworzy link") and resource, and splits the output into two concrete variants: a free review with prefilled address and problem (typ=przeglad) or a cart with a chosen service (typ=zamowienie). What is missing is any differentiation from siblings such as dobierz_usluge or cennik, so an agent cannot tell from this text alone which tool to reach for when it needs service selection instead of link creation.

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 two typ values are described well enough that an agent can pick between a review link and an order link, and the closing sentence sets the expectation that a human confirms consents and the order. There is no explicit when-to-use or when-not-to-use statement, and no pointer to an alternative tool for related tasks.

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