Skip to main content
Glama

MonoEsim — Travel Connectivity for AI Agents

Affiliate sales and commission

list_affiliate_sales
Read-onlyIdempotent

List sales made through your referral link (latest first, 50 per page): date, destination, plan, amount, refunds, your commission and its state (held, available, settled, void). Contains no customer data. Requires an active affiliate key.

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

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page; use next_page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavior: latest-first ordering, 50-per-page pagination, an active-affiliate-key auth requirement, and an explicit privacy guarantee ("Contains no customer data"). It also enumerates the returned fields, including commission state values (held, available, settled, void), which is meaningful for interpreting results.

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?

One sentence plus a parenthetical, front-loaded with the verb and resource, then paging, then returned fields, then the auth constraint. Every clause carries information and none is redundant.

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?

There is no output schema, but the description compensates by enumerating the returned fields and the commission-state vocabulary, and it covers the auth prerequisite and paging model. For a single-optional-parameter read tool, nothing an agent needs in order to call it correctly is missing.

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?

Schema coverage is 100% and there is only one parameter, so the baseline is 3. The description earns a bump by disclosing the page size (50 per page) and result ordering, which the schema's "Zero-based page" note does not convey and which is needed to reason about paging.

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?

States a specific verb and resource ("List sales made through your referral link") and immediately scopes it with ordering, page size, and the exact fields returned. That scope distinguishes it cleanly from siblings like list_destinations and get_order without needing to name them.

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 clear context for use: it returns sales from your referral link and requires an active affiliate key, which is a real prerequisite an agent could otherwise miss. It stops short of naming alternatives or stating when-not-to-use, so it lands at a clear-context-but-no-exclusions 4.

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