Skip to main content
Glama

Zoya.bg

shopping_context

Read or explicitly save up to 20 product references, after user consent. No cached prices.

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

Input Schema

NameRequiredDescriptionDefault
storefrontNozoya.bg
product_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose important traits: user consent is required, at most 20 references are handled, and no cached prices are used. It does not explain whether saving overwrites existing context, how persistence works, or what permissions are needed.

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?

The description is two short, front-loaded sentences with no filler. The compressed phrasing 'read or explicitly save' is efficient but leaves the mode-selection logic ambiguous.

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

Completeness2/5

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

For a two-parameter context tool with no annotations and no output schema, the description is not complete enough. It omits parameter behavior, read-versus-save semantics, and what context is returned, so an agent would have to guess how to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for both parameters. It never explains 'storefront' or 'product_ids', including whether null product_ids means read mode or supplied IDs trigger save mode, leaving only the 20-item cap as added meaning.

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

Purpose3/5

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

The description states that the tool reads or explicitly saves product references with a 20-item cap, which gives some specific purpose. However, 'shopping_context' remains vague, and the dual read/save behavior is not clearly resolved or differentiated from siblings such as shopping_cart or cart_history.

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 consent prerequisite and the 20-reference limit provide useful usage context. Still, there is no explicit guidance on when to use this rather than shopping_cart, cart_history, preferences, or other sibling tools, nor when not to use it.

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