Skip to main content
Glama
Sign In

Free Agent Tools

by io.github.akiba-labs
OverviewDiscussionsAdmin

What is an old email list worth?

email_list_reactivation_value
Read-onlyIdempotent

Estimates buyers and revenue from one offer to past customers in low / mid / high scenarios, with an optional partner revenue share.

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": {
      "contacts": "<contacts>",
      "orderValue": "<orderValue>"
    },
    "name": "email_list_reactivation_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyRateNoExpected percent of reached contacts who buy. Default 1.
contactsYesNumber of past contacts.
reachableNoPercent of contacts still reachable. Default 70.
orderValueYesAverage order value of the offer.
partnerShareNoOptional partner revenue share percent. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare a safe, idempotent, closed-world read operation, so the safety profile is covered. The description usefully adds that results come in low/mid/high scenarios and that a partner share can be applied, but it does not explain what the returned figures represent or how the scenarios are derived.

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 dense sentence with the estimation target front-loaded and the optional partner-share modifier at the end. Nothing is wasted, though the phrase 'in low / mid / high scenarios' is slightly ambiguous about whether scenarios are inputs or outputs.

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?

With no output schema, the description carries more of the burden for explaining results, and it only gestures at the return (buyers, revenue, three scenarios) without saying what each scenario contains or how partnerShare affects the numbers. Adequate for a read-only calculator but leaves the output shape underspecified.

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 description coverage is 100%, so every parameter (buyRate, contacts, reachable, orderValue, partnerShare) is already documented with defaults and ranges. The description only echoes partnerShare and orderValue at a high level, adding no syntax or constraint detail beyond the schema.

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?

Specific verb ('Estimates') plus a concrete resource (buyers and revenue from one offer to past customers), with scenario framing that clearly marks it as a calculator. It is easily separable from sibling calculators like price_headroom_check or thirty_day_cash_check, though it never names an alternative explicitly.

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

Usage Guidelines2/5

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

The description says what is computed but gives no when-to-use context, no prerequisites, and no indication of when this model is or is not appropriate versus the other estimate/calculator siblings. Usage must be inferred entirely from the tool name.

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

All Free Agent Tools 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