Skip to main content
Glama

Lepiej Widoczny – audyt WordPress/WooCommerce

Cennik usług Lepiej Widoczny

cennik
Read-onlyIdempotent

Pełny cennik usług Lepiej Widoczny (modernizacja stron i sklepów WordPress/WooCommerce): ceny końcowe w PLN, czas realizacji, warunki płatności (usługi jednorazowe po odbiorze, opieka z góry) i linki do zamówienia.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cennik"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false, so safety needs no restating. The description adds genuine behavioral context beyond that: it discloses that prices are final ('ceny końcowe'), currency is PLN, and that payment terms differ by service type (one-off paid on delivery, retainer paid upfront), plus that order links are included.

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 naming the resource first, then the covered content in a compact parenthetical. It is dense but every clause carries information; the nested parenthesis about payment conditions makes it slightly harder to scan than it needs to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no input parameters and no output schema, the description carries the burden of explaining what comes back, and it does so concretely by enumerating prices, delivery time, payment terms, and order links. Nothing an agent needs in order to call it and interpret the result is missing.

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?

The tool takes zero parameters, so there is no parameter meaning the description could add; the baseline for a no-parameter tool applies. The description correctly gives no argument guidance, consistent with the empty 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?

States a specific resource ('Pełny cennik usług Lepiej Widoczny') with domain scope (modernizacja stron i sklepów WordPress/WooCommerce) and the exact contents: final PLN prices, delivery time, payment terms, order links. It does not explicitly contrast with siblings such as 'dobierz_usluga' or 'opis_standardu', but the resource is distinct enough that an agent can tell it is the pricing source rather than a service-selector or spec document.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement and no named alternative or exclusion. Usage is only implied by the word 'cennik' and the mention of order links; an agent must infer that this is the tool for price questions and not for service selection or audits.

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