Skip to main content
Glama

transactions

Derniers achats du compte.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden and discloses almost nothing: it does not confirm the operation is read-only, whether results are scoped to the authenticated user, how they are ordered, or how many are returned. Only the vague notion of 'derniers' hints at recency / implicit ordering.

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

Conciseness3/5

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

The definition is a single short sentence with no filler, so it is concise, but it is under-specified rather than efficient because it front-loads nothing about scope, count, or ordering.

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

Completeness2/5

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

For a data-retrieval tool with one undocumented parameter, no annotations and no output schema, the description leaves out the essentials: what a 'purchase' record contains, whether the account is implicit, and how results are limited or ordered.

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 coverage is 0% for the single parameter 'limit', and the description never mentions it. An agent can guess that limit caps the number of purchases returned, but neither the meaning, default, nor valid range is stated in either the schema or the description.

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

Purpose3/5

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

The sentence 'Derniers achats du compte' identifies a resource (recent purchases belonging to the account) but supplies no verb to indicate whether it lists, retrieves, or aggregates them. It is distinguishable from siblings like buy or order_status by implying a historical read, though the French wording versus English sibling names adds friction.

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

Usage Guidelines2/5

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

There is no statement of when to use this over fetch-style alternatives such as order_status or search_tools, and no prerequisites or exclusions are given. The only implied guidance is that the tool concerns the current account, which an agent must infer.

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