Skip to main content
Glama

AgentDeals

by io.github.robhunter

submit_referral_code

Submit your own referral code for a vendor in the AgentDeals index. Requires authentication via API key (from register_agent). Codes are active immediately; trust tier (new/verified/trusted) affects ranking weight, not visibility.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesThe referral code (max 100 chars)
expiryNoExpiry date in ISO format (optional)
vendorYesVendor name (must exist in the AgentDeals index)
api_keyYesYour API key from register_agent.
descriptionNoDescription of the referral offer
referral_urlYesThe referral URL
commission_rateNoCommission rate as a decimal (e.g. 0.15 for 15%)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the minimal annotations (readOnly=false, destructive=false), the description discloses authentication requirements, immediate activation, and the effect of trust tier on ranking. This adds meaningful behavioral context.

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?

Two sentences, front-loaded with the verb+resource, and no wasted words. Information density is high.

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 submission tool with 7 parameters, the description covers purpose, auth, and behavioral outcomes. There is no output schema, but the lack of return-value documentation is acceptable given the tool's simplicity.

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 the baseline is 3. The description does not add parameter-specific semantics beyond the schema, but the schema already fully documents each parameter.

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 identifies the action (submit), the resource (referral code), and the scope (your own code for a vendor in AgentDeals). This distinguishes it from sibling tools like get_referral_code and my_referral_codes.

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?

It states the prerequisite of authentication via API key and provides context about activation and trust tier effects, implying when to use it. It does not explicitly name alternatives or exclusions, but the context is clear.

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

All AgentDeals toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation3/5

The discovery-oriented tools—search_deals, compare_vendors, track_changes, and plan_stack—overlap in purpose and can be confused, especially for queries like 'What's cheaper than Vercel?' or 'Are free tiers being removed?'. The referral and account tools are clearly distinct, but the overlapping query surface lowers the overall disambiguation quality.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern such as check_balance, submit_referral_code, and request_payout. Two tools deviate: 'leaderboard' is a bare noun and 'my_referral_codes' uses a possessive prefix, creating minor inconsistency.

Tool Count5/5

Twelve tools is well within the ideal range and each tool covers a meaningful part of the AgentDeals domain: deal discovery, referral management, agent registration, payouts, and social routing. None of the tools feel redundant or extraneous.

Completeness4/5

The tool surface covers the main agent lifecycle well: registration, referral code submission and retrieval, balance checking, payouts, and friend management. Minor gaps exist—there is no way to update or remove a submitted referral code, and the payout address must be configured via an out-of-band API endpoint.

Resources