Skip to main content
Glama

MonoEsim — Travel Connectivity for AI Agents

Join the affiliate programme

register_affiliate

Register this AI agent as a MonoEsim affiliate (call WITHOUT an API key). Pass the email of the human who owns you, your name, where and how you will promote MonoEsim, and accept_program_rules=true after reading the rules. Returns a one-time API key at once; the owner must confirm by email before referral links and commission work. Payouts go only to payout details the owner saves in the partner portal.

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": {
      "owner_email": "<owner_email>",
      "agent_name": "<agent_name>",
      "promotion_plan": "<promotion_plan>",
      "accept_program_rules": "<accept_program_rules>"
    },
    "name": "register_affiliate"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage for names and texts (default en).
agent_nameYesYour public name, e.g. 'TripBot on Telegram'.
owner_emailYesEmail of the human owner; they confirm and receive the payouts.
promotion_planYesWhere and how you will promote MonoEsim (channels, audience). Spam is forbidden.
accept_program_rulesYestrue only after reading the program rules (no spam, ads marked as ads, no brand bidding, real prices only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, idempotentHint=false and openWorldHint=true; the description adds the genuinely useful lifecycle detail the agent cannot get elsewhere: an immediate one-time API key, a pending state until the owner confirms by email, and that links/commissions stay inert until then. It does not say what a second call does to an existing affiliate or whether re-registration duplicates the account, which matters given idempotentHint=false.

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?

Four compact sentences with zero filler, and the highest-risk constraint ('call WITHOUT an API key') is front-loaded in parentheses where it will be read first. Every sentence carries distinct information: auth mode, inputs, return/timing, payout routing.

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

Completeness4/5

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

For a multi-step registration with a delayed activation state and no output schema, this covers the critical path well, including the immediate API-key return and the email-confirmation gate. The notable gap is the instruction 'after reading the rules' without pointing at the tool that serves them (get_terms / card_payment_terms siblings), leaving the agent to guess where the rules live.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so every parameter is already documented, and the description largely restates them (owner email, agent name, promotion plan, accept_program_rules). The one real addition is the dependency that the owner_email recipient is the person who must confirm and receive payouts, but overall it stays at the baseline for a fully covered schema.

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?

Names a specific verb and resource ('Register this AI agent as a MonoEsim affiliate') and scopes it as a one-time enrolment that yields an API key, which cleanly separates it from get_affiliate / list_affiliate_sales / get_referral_link. An agent can identify the operation without opening the schema.

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 a concrete invocation condition rarely stated elsewhere: call WITHOUT an API key, and only set accept_program_rules=true after actually reading the rules. It stops short of naming the alternative for agents that are already registered (e.g. get_affiliate), so there is a small inference gap.

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