Skip to main content
Glama

MonoEsim — Travel Connectivity for AI Agents

Affiliate status, link and balance

get_affiliate
Read-onlyIdempotent

Read your affiliate account with your API key: state (awaiting_owner_confirmation, active, pending_review, blocked), referral link and ?ref= code, QR image, clicks and sales, balance in EUR (available, on hold, processing, paid), and whether your owner completed the payout setup. Read-only; customer data is never included.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description goes beyond them by adding the auth requirement (API key), a full enumeration of the possible account states, the balance sub-buckets, and the privacy guarantee that customer data is never included. That privacy and state-machine context is genuinely additive. It does not discuss rate limits or what happens for a non-affiliate caller.

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?

A single front-loaded sentence with the verb and resource first, followed by the payload enumeration and the privacy caveat. Dense but every clause carries information. The nested parenthetical lists are heavy for one sentence but remain scannable.

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?

With no parameters, no output schema and rich annotations, the description's main job is to convey what comes back and under what constraints — and it enumerates the entire response surface, including enum states and balance buckets. Nothing an agent needs in order to call this zero-arg read 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The sentence about using your API key correctly frames the only implicit input as the credential.

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 ("Read") and resource ("your affiliate account") and then enumerates exactly what is returned: state values, referral link and ?ref= code, QR image, clicks and sales, EUR balance breakdown, and payout-setup flag. An agent knows precisely what payload to expect. It stops short of distinguishing itself from siblings like get_referral_link or list_affiliate_sales, which overlap on parts of the returned data.

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?

Usage is only implied: you call it to read affiliate status with your API key, and the read-only note signals it is a non-mutating lookup. There is no explicit statement of when to prefer this over get_referral_link (for the link alone) or list_affiliate_sales (for sales detail), nor any prerequisite such as needing an existing affiliate registration.

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