Skip to main content
Glama

Lepiej Widoczny – audyt WordPress/WooCommerce

Fetch (poradnik Lepiej Widoczny)

fetch
Read-onlyIdempotent

Fetch full content of a Lepiej Widoczny guide or page by id (URL) returned from search.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

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=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds that the operation returns full page content keyed to a URL, which is genuine added context, but says nothing about truncation, size limits, or behavior when the id is stale or invalid.

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?

A single front-loaded sentence that states the action, the resource, and the identifier origin with zero filler. Nothing could be removed without losing information.

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 full annotation coverage and no output schema, the description supplies what matters: what is returned (full content) and where the id comes from (search results). Error handling for invalid ids is the only notable omission.

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 coverage is 0% and the single parameter is bare, so the description must carry the load; it does clarify that the id is a URL originating from search results, which is meaningful beyond the schema. It still leaves ambiguity about the exact format (full absolute URL vs slug) and any encoding expectations.

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 ('Fetch') and resource ('full content of a Lepiej Widoczny guide or page'), and clarifies it returns entire content rather than snippets, which distinguishes it from a search tool. It stops short of naming or contrasting any sibling tool by name, so an agent must rely on the shared workflow hint ('returned from search') to disambiguate.

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 implied rather than stated: the phrase 'id (URL) returned from search' tells the agent this is the follow-up step after a search, which is a useful precondition. However, there is no explicit 'use this when you need full text rather than a summary' framing and no when-not guidance or named alternative.

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