Skip to main content
Glama

buy

Acheter et exécuter un outil. Débite le portefeuille, applique la politique de dépense du compte, rembourse automatiquement en cas d'échec. Au-delà du seuil de validation, l'achat attend une validation humaine.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tool_id": "<tool_id>"
    },
    "name": "buy"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNo
tool_idYes
max_price_eurNoRefuse l'achat si le prix dépasse ce montant

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description itself provides valuable side-effect context: wallet debit, account spending-policy enforcement, automatic refund on failure, and human approval above a threshold. It does not explain whether approval or execution is asynchronous, how to track a pending purchase, or whether effects of the executed tool are reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three compact, front-loaded sentences: action first, then financial and failure behavior, then approval gating. There is no filler or repetition, and each sentence adds useful information.

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 tool that both spends money and executes another tool, the core transactional behavior is covered, but operational details such as the validation threshold's source, pending-order tracking, execution status, and the shape of params remain absent. With no annotations or output schema and only 33% parameter coverage, it is usable at a high level but incomplete for confident end-to-end invocation.

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?

Only max_price_eur is documented in the schema, and the description adds no parameter-specific guidance. In particular, tool_id lacks source or format guidance, while the nested params object gives no indication of the expected execution arguments or how they are validated.

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 opening "Acheter et exécuter un outil" states a specific action pair and resource, making clear that this is a purchase-plus-execution operation. It does not explicitly differentiate itself from siblings such as find_and_buy or explain its place in a discovery or quotation workflow.

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 wording implies use when the caller wants to buy and execute a selected tool, and the approval rule supplies a relevant conditional. However, there is no explicit guidance on prerequisites, when not to buy, or when to use another tool for discovery, quotation, or status handling.

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