Skip to main content
Glama

Zoya.bg

show_cart

Use for every request to show the active basket, including “покажи ми кошницата”, “какво има в количката” and greetings with a basket request. Open the Zoya component with photos, quantities and prices. In a new conversation call session_start first, then call this tool directly. Requires sign-in.

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

Input Schema

NameRequiredDescriptionDefault
languageNobg

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does meaningful work: it discloses what the user sees (component with photos, quantities, prices), an authentication requirement ('Requires sign-in'), and a prerequisite dependency on session_start. It stops short of covering read-only semantics, failure modes, or what happens when the cart is empty.

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?

Four compact sentences, front-loaded with the trigger condition, then outcome, then prerequisites. The quoted multilingual examples consume space but serve a real routing function; the auth note at the end could sit closer to the other prerequisite statement.

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?

This is a simple, low-parameter read tool with no output schema, and the description covers purpose, user-visible result, auth, and conversation-start ordering. The only notable gap is the undocumented language parameter, which is minor for a one-optional-param tool.

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 0% for the single optional 'language' parameter (default 'bg'), and the description never explains it. The Bulgarian example phrases implicitly signal the expected language context, which is partial compensation, but an agent still must inspect the schema to learn the parameter exists.

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 definition states a specific verb and resource: showing the active basket/cart, and it describes the concrete outcome ('Open the Zoya component with photos, quantities and prices'). It does not name or distinguish itself from plausible siblings such as shopping_cart or cart_history, so differentiation is left to inference.

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?

It gives explicit trigger conditions ('every request to show the active basket') and even lists example user utterances, plus a concrete sequencing rule: call session_start first in a new conversation, then this tool. What's missing is a when-not-to-use clause or an explicit statement of how it differs from the other cart-related siblings.

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