Skip to main content
Glama

Lepiej Widoczny – audyt WordPress/WooCommerce

Pobierz poradnik

pobierz_poradnik
Read-onlyIdempotent

Zwraca pełną treść poradnika (lub innej strony lepiejwidoczny.pl) w Markdown – podaj adres albo slug.

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": {
      "adres": "<adres>"
    },
    "name": "pobierz_poradnik"
  }
}

Input Schema

NameRequiredDescriptionDefault
adresYesAdres URL albo slug poradnika.

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value by stating the return format (full content, Markdown) and that the content is not truncated, but it says nothing about failure behavior for an invalid or external адрес, which matters given openWorldHint=false.

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?

One sentence, front-loaded with the result and format, ending with the input hint. There is no redundant or filler wording.

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 tool with full annotation coverage and no output schema, the description supplies the essential missing piece – what comes back (full page content in Markdown). Only edge-case behavior (bad slug, off-site URL) is absent, which is a minor gap.

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?

Schema description coverage is 100% and the single parameter already documents 'Adres URL albo slug poradnika', so the description's 'podaj adres albo slug' largely restates the schema. Baseline 3 applies because the schema does the heavy lifting.

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 (returns) and resource (full guide content), and adds the output format (Markdown) plus a domain scope (poradnik or another lepiejwidoczny.pl page). That scoping implicitly separates it from a generic fetch or from szukaj_poradnikow, though it never names a sibling 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 agent can infer 'call this to read a specific guide you already have the address for'. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as a search tool for when the slug is unknown – the closing phrase is a parameter instruction, not guidance.

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