Skip to main content
Glama

Aident AI

by ai.aident.loadout
OverviewDiscussionsAdmin

affiliate

Activate or inspect your Loadout affiliate account, request a payout, or permanently attach an affiliate code within 60 days of signup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoAffiliate code to redeem
actionNostatus
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
termsAcceptedNoConfirms acceptance of https://aident.ai/affiliate-program-terms version 2026-08-15

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
    • addedInput schema / properties / llm_model
      Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "context",
+  "llm_model"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "activate",
-  "status",
-  "redeem"
-]New value: +[
+  "activate",
+  "status",
+  "redeem",
+  "request-payout"
+]
    • changedInput schema / properties / termsAccepted / description
      Previous value: -"Confirms acceptance of https://aident.ai/affiliate-program-terms version 2026-08-11"New value: +"Confirms acceptance of https://aident.ai/affiliate-program-terms version 2026-08-15"
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

The description adds behavioral context beyond annotations by highlighting 'permanently attach' (irreversible action) and the 60-day signup window. This is useful, though it does not fully disclose all side effects or prerequisites (e.g., terms acceptance). No contradiction with annotations (readOnlyHint=false, destructiveHint=false) since the actions are mutations but not destructive.

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?

A single, efficient sentence that front-loads the core actions and the time constraint without extraneous fluff. Every clause contributes to understanding the tool's purpose and scope.

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?

The description is adequate but incomplete for a tool with five parameters and no output schema. It does not mention that termsAccepted must be true for certain actions, nor does it clarify which actions require which parameters. It also omits any indication of the return value, leaving the agent to infer behavior from the schema alone.

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?

The schema covers 80% of parameters with descriptions, and the description provides high-level context that maps to the action enum (activate, status, redeem, request-payout). However, it does not elaborate on parameter-specific requirements, combinations, or the analytics-only parameters (context, llm_model) beyond what the schema states. The description adds minimal value beyond the 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?

The description clearly states the tool's function: 'Activate or inspect your Loadout affiliate account, request a payout, or permanently attach an affiliate code.' It names a specific resource (affiliate account) and lists distinct actions, distinguishing it from sibling tools like billing or auth. The 60-day constraint adds specificity.

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 description implies use for affiliate account management but does not explicitly state when to use this tool over alternatives, nor does it mention exclusions or when not to use it. It lacks comparative guidance against siblings such as billing or auth.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Aident AI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources