Skip to main content
Glama

Lepiej Widoczny – audyt WordPress/WooCommerce

Standard LW Audit

opis_standardu
Read-onlyIdempotent

Opis otwartego standardu LW Audit (CC BY 4.0): kategorie, testy z identyfikatorami, progi, wagi i zasady oceny.

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": "opis_standardu"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description contributes genuine extra context by stating the standard is open and licensed CC BY 4.0, which matters for reuse of the returned content, but it says nothing about the shape or size of the response.

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 sentence that front-loads the resource, then lists the five content areas, then closes with the license. Every clause carries information; nothing is repeated from the title or annotations.

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

Completeness3/5

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

There is no output schema, so the description bears the burden of telling an agent what it will get back. Listing categories, identifiers, thresholds, weights and scoring rules does that at a content level, but it never states the return format (structured data vs. prose document) or how large the payload is, which for a no-argument reference tool is a meaningful gap.

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 semantics to add and the baseline of 4 applies. The description's enumeration of content areas does not map to any inputs and correctly makes no attempt to describe arguments.

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 the resource precisely (the open LW Audit standard) and enumerates its content: categories, tests with identifiers, thresholds, weights and scoring rules. That is far more specific than a tautology such as 'returns the standard'. It stops short of a 5 because it never contrasts itself with siblings like audyt_strony or plan_poprawy, which evidently depend on this standard.

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 'opis otwartego standardu' tells an agent this is the reference source for the audit methodology, so it should be consulted when definitions of tests, thresholds or weights are needed. There is no explicit when-to-use, when-not-to-use, or routing to alternatives, so it cannot rise above implied 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