Skip to main content
Glama

Zoya.bg

personalization

Read the private shopping profile, enabled by default for signed-in users. Existing opt-outs are preserved. Enable resumes learning from product views, individual selections and explicit removals. Disable deletes signals and stops collection. Forget clears signals while preserving the current status. forget_product removes all signals for one exact product_id and storefront, preserving other products and the enabled status. Conversation memory is controlled separately. Never infer medical conditions or purchases.

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

Input Schema

NameRequiredDescriptionDefault
actionNoread
product_idNo
storefrontNozoya.bg

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/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 substantial work: it discloses that opt-outs are preserved, that Disable deletes signals AND stops collection, that Forget clears signals but retains status, that forget_product is scoped to one exact product_id plus storefront, and that it must not infer medical conditions or purchases. Remaining gaps are auth requirements, rate limits, and what a read returns, but the destructive-action semantics are unusually well disclosed.

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 resource and default state are front-loaded in the first sentence, then each action gets one compact clause in a logical order. It is dense but nearly every sentence carries distinct information; 'Never infer medical conditions or purchases' reads more like model policy than tool behavior but is short and privacy-relevant.

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?

For a no-annotation, no-output-schema tool with three undocumented parameters, the description covers side effects and action semantics well but omits return shape and the literal action values an agent must pass. It is adequate to avoid destructive mistakes, but not sufficient to call the tool confidently on the first attempt.

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 coverage is 0% and the 'action' property is a bare string with no enum, so the description does valuable work by surfacing the candidate operations (read/enable/disable/forget/forget_product) and by binding product_id and storefront together for the product-level case. It still leaves the exact literal values and casing ambiguous, and never states storefront's format or that product_id is only meaningful for forget_product.

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 a specific resource ('the private shopping profile') and enumerates concrete operations (read, enable, disable, forget, forget_product), so an agent can tell it manages personalization signals rather than conversation memory. The opening sentence is framed as policy ('enabled by default for signed-in users') rather than as a clean statement of what the tool does, which slightly blurs the purpose statement.

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?

It gives per-action semantics that imply when to use each mode (e.g. 'Forget clears signals while preserving the current status'), and 'Conversation memory is controlled separately' implicitly routes memory-related work elsewhere. However, it never states when to prefer this tool over siblings like preferences or shopping_context, and the memory-routing hint does not name the actual alternative.

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