Skip to main content
Glama
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k

get_source_cart

Read-only

Retrieves all cart global sources in a compact tree view, showing the full element hierarchy so you can inspect cart structure without separate detail calls.

Instructions

Get all cart global sources with compact tree view. Shows full element hierarchy — no need to call get_global_source_detail separately.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.8.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv1.31.8

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the description only needs to add context. It contributes the return shape (a compact tree that nevertheless contains the full element hierarchy), which is useful given there is no output schema. It says nothing about size, depth limits, or ordering of a potentially large tree.

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?

Two short sentences with no filler; the primary purpose is front-loaded and the secondary sentence adds routing value rather than restating the name. Slightly more compact phrasing could fold both ideas into one line, but nothing is wasted.

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?

For a no-parameter, read-only retrieval with no output schema, the description supplies what matters: what comes back (a full hierarchical tree) and that it subsumes a detail call. Only minor gaps remain around result size and structure limits.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline of 4 applies; the description correctly implies a call with no scoping arguments.

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 a specific verb and resource ("Get all cart global sources") and adds the shape of the result ("compact tree view" with full element hierarchy). It even names a related tool it replaces, so an agent can distinguish it from detail-oriented siblings, though the domain term "global sources" is jargon that isn't unpacked.

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 line "no need to call get_global_source_detail separately" gives an explicit exclusion against one alternative, which is genuine routing guidance. However, it offers no positive condition for when to choose this over other source/context tools such as global_source or get_current_context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.