Skip to main content
Glama

www.cerano.pl catalog

Ask Business

ask_business
Read-onlyIdempotent

Answer questions about the shop itself (shipping, payment, returns, complaints, warranty, installation) with verbatim snippets from the shop's published pages and articles, each with its URL (snippets may be empty for a page without quotable text, e.g. a form: link it). Quote or paraphrase only these snippets and link the URL; when answers is empty, the answer could not be found in the published information: say so and give the contact.

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": {
      "request": "<request>"
    },
    "name": "ask_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/closed-world, and the description goes well beyond them: it explains that answers are grounded verbatim in published pages with URLs, that snippets may be empty for form pages (link them anyway), and that an empty answers collection means the question is unanswerable — respond with that and the contact. These are real operating rules an agent must follow, not restated field metadata.

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 dense sentence that front-loads the purpose before the grounding and fallback rules. Every clause carries information, though the run-on structure makes the fallback rule easy to skim past.

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 an output schema covering the return shape and annotations covering safety profile, the description supplies exactly the missing pieces: source grounding, empty-snippet handling, and the not-found fallback. Nothing needed to call it correctly is absent.

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?

Only one nested parameter exists and the schema already documents its question field with examples and length bounds. The description adds the constraint that the question must concern the shop's own policies, slightly narrowing intent beyond the schema, though it does not add language/format detail the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ("Answer questions about the shop itself") and enumerates the exact domains covered (shipping, payment, returns, complaints, warranty, installation), which cleanly separates it from catalog/order siblings. An agent can tell this is a policy/information Q&A tool without opening the schema.

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

Usage Guidelines4/5

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

The topic list effectively defines when to call it: shop-level questions rather than product or order lookups. It gives no explicit exclusion or named alternative, so it stops short of full routing guidance, but the scope is unambiguous.

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