Skip to main content
Glama

Lepiej Widoczny – audyt WordPress/WooCommerce

Profil sklepu dla asystentów AI

profil_dla_ai
Read-onlyIdempotent

Generuje z publicznych danych sklepu gotowe do wklejenia materiały, dzięki którym asystenci AI (ChatGPT, Claude, Gemini, Perplexity) lepiej zrozumieją ofertę: plik llms.txt (opis, kategorie, popularne produkty, dostawa, zwroty, kontakt), dane firmy w JSON-LD (OnlineStore z kontaktem, NIP i polityką zwrotów) oraz szkic FAQ z FAQPage. Miejsca do uzupełnienia są oznaczone [Uzupełnij: …].

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": {
      "url": "<url>"
    },
    "name": "profil_dla_ai"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAdres strony lub sklepu, np. twoj-sklep.pl

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, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behaviour the annotations cannot convey: output is generated only from public shop data, it comes in 'ready to paste' form across three named formats, and gaps are flagged with '[Uzupełnij: …]' placeholders. It still does not say whether results are returned as text or written somewhere, but the added context clearly exceeds the annotation baseline.

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?

One dense but well-ordered sentence: the action and data source come first, the three deliverables follow parenthetically, and the placeholder convention closes it out. The parenthetical enumeration is long but every item earns its place by telling the agent what it will get back; no filler or repetition.

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 generation tool with no output schema, the description gives a full inventory of what is produced and how incomplete sections are marked. The only real gap is the delivery mechanism (returned text vs. stored file) and whether the target URL must be publicly reachable, which matters for a tool built on public data.

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 url parameter already carries an example ('twoj-sklep.pl'), so the schema does the heavy lifting. The description adds no further syntax, domain-normalisation or reachability constraints for the input, making the baseline 3 correct.

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 opens with a specific verb and scope ('Generuje z publicznych danych sklepu') and then enumerates the exact deliverables: llms.txt with description, categories, popular products, shipping, returns and contact; JSON-LD OnlineStore with NIP and return policy; FAQ draft with FAQPage. That level of concrete output detail makes the tool's purpose unmistakable, though it never names a sibling to contrast with.

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?

The intended use case is implied by the stated goal (helping AI assistants such as ChatGPT, Claude, Gemini and Perplexity understand the offer), which is enough to infer when to reach for it. There is no explicit when-not guidance and no routing away from neighbouring tools like audyt_strony or opis_standardu, so the agent must infer selection itself.

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