Skip to main content
Glama

Coșul (ce e pregătit și n-a plecat)

get_cart
Read-onlyIdempotent

Articolele cu site-uri pregătite care încă n-au plecat (după un refuz pentru sold, un coș venit de la un site partener sau o selecție salvată) și proformele neplătite. asteaptaPlata pe un articol înseamnă că pleacă singur după confirmarea plății proformei.

Use when the user asks what is pending, waiting for payment or prepared but not sent, or after an order was refused for insufficient balance. Do not use for publications already sent: use list_publications.

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_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
itemsNoarray of {articleId, title, sites: [{siteId, name, url}], asteaptaPlata: {reference, grossCents}|null}. Prepared, not yet sent.
proformeInAsteptareNoarray of {id, reference, grossCents, currency, expiresAt, articleId}. Unpaid proformas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds genuine domain behavior beyond that: what populates the cart and the meaning of the `asteaptaPlata` flag (the item departs automatically once the proforma payment is confirmed), which tells the agent the cart is a live pre-publication queue rather than a static list.

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?

Content is front-loaded: what the cart contains, then the field semantics, then when to use and when not to. The first sentence is dense with parenthetical enumerations, but every clause carries information; nothing is filler.

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

Completeness5/5

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

For a zero-parameter read with an output schema already present, the description supplies everything needed: scope of results, the meaning of the key state field, and correct routing away from list_publications. Return-value formatting is rightly left to the output schema.

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 and the baseline of 4 applies. No parameter-related noise was added either.

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

Purpose5/5

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

The description names the exact resource contents: articles with prepared sites that have not departed (after a balance refusal, a partner-site cart, or a saved selection) plus unpaid proformas. It also explicitly separates itself from list_publications ('publications already sent'), so an agent can route correctly without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete when-to-use triggers ('what is pending, waiting for payment or prepared but not sent, or after an order was refused for insufficient balance') and an explicit when-not with the named alternative ('Do not use for publications already sent: use list_publications'). Both the positive and negative routing conditions are stated.

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.