Skip to main content
Glama

Zoya.bg

cart_history

Member-private Firebird cart history, not confirmed orders. Actions list/get; repeat merges fresh-verified items into current draft only; set_preference records explicit cart-history consent; forget_all deletes history and disables future saving, only on explicit user instruction. Saving is opt-in at transfer. A previously explicitly enabled preference checks the next form by default. Never say a purchase was completed. Never repeat/clear history merely because session_start reports it exists.

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

Input Schema

NameRequiredDescriptionDefault
actionNolist
enabledNo
before_idNo
history_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 behavioral burden and discloses privacy scope, opt-in saving, destructive deletion via forget_all, disabling future saving, repeat merging only into the current draft, and the prohibition on claiming a completed purchase. It omits error/permission details and return behavior, but provides substantial behavioral context.

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 identity and the 'not confirmed orders' distinction are front-loaded, followed by action semantics and then safety rules. The prose is dense but every sentence carries a behavioral or safety constraint, with little wasted wording.

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 multi-action tool with a destructive forget_all and no annotations or output schema, the description covers consent, deletion safeguards, and privacy well. However, it leaves parameter-level semantics and return behavior unclear, which are significant gaps for an agent invoking 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 all four parameters. It names action behaviors but does not map enabled, before_id, or history_id to their meanings, nor does it explain pagination or lookup semantics; it only partially compensates by describing what some actions do.

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?

States the resource as member-private Firebird cart history and explicitly distinguishes it from confirmed orders, then enumerates the actions list/get, repeat, set_preference, and forget_all. It does not name sibling alternatives such as show_cart or shopping_cart, but the tool's domain and scope are clear.

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?

Gives explicit constraints for repeat, set_preference, and especially forget_all ('only on explicit user instruction'), and warns against repeating or clearing history merely because session_start reports it exists. It does not explicitly route between list/get and sibling cart-viewing tools, so it stops short of full alternative guidance.

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