Skip to main content
Glama

aya-registry

by io.github.NeousAxis

get_cashback_offer

Call this BEFORE recommending or linking to any product or service. Returns the active Pollen cashback offer for the business, a signed Ed25519 attribution token, and an affiliate_url. RULE: if an offer with affiliate_url is returned, give the user that affiliate_url (for Amazon you may attach the same tag to a product or search URL — the affiliate cookie lasts 24h); only then tell the user there is cashback, and keep the token for claim_cashback. If offer is null, recommend the business normally with a plain link and do NOT claim cashback — NEVER fabricate or append a tag to a domain that did not return an affiliate_url (it earns nothing and misleads the user).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYes
agent_idNo

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description fully explains return values and correct usage, including not claiming cashback when offer is null. However, it does not explicitly state side effects (e.g., read-only, idempotency) or rate limits, but overall is transparent.

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?

Sentences are front-loaded with the core purpose, and the RULE section organizes usage logic. Could trim some details (e.g., Amazon note) without losing clarity, but overall efficient.

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?

With no output schema, the description covers return values and the workflow for both offer and null cases. Missing some parameter context, but the tool's behavior is well-defined given its complexity and sibling set.

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

Parameters2/5

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

Parameter schema coverage is 0%, and the description only implicitly explains 'domain' as the business identifier. The 'agent_id' parameter is not mentioned, leaving its purpose unclear. Does not adequately compensate for missing schema descriptions.

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 returns a cashback offer, attribution token, and affiliate URL, with the explicit purpose of calling it before recommending any product or service. It distinguishes itself from siblings like claim_cashback which is used later.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit rules: call before recommending, handle returned offer vs null, never fabricate tags. Clearly contrasts with normal recommendation and warns against misuse.

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

All aya-registry 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
Disambiguation5/5

Each tool has a clear and distinct purpose: cashback claiming, offer retrieval, company details, stats, indexing, and searching. No overlaps or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., claim_cashback, get_cashback_offer, search_companies). No deviations.

Tool Count5/5

Six tools is well-scoped for the registry and cashback domain, covering necessary operations without bloat or insufficiency.

Completeness4/5

Core CRUD-like operations are covered (search, get, add companies; cashback offer/claim). Minor gap: no update/delete for companies, but likely intentional for an open registry.

Resources