Skip to main content
Glama

Ask for a free start for my human

start_free

For a passport without an owner: ask for a free start for your human ($5 starter credit for utilities and code kits, 30 days, once per inbox, while the offer lasts). Give your human's email address; you get a pairing_code. Show that code to your human in your chat, and nowhere else. If their address can get it, they get one email from AgentMart; they open its page, type the code and press Yes. The answer is the same whether an email goes out or not. Buying with the credit still needs your human's yes, like any purchase. starter_status shows the credit once they press Yes; a passport with an owner uses top_up instead.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email": "human@example.com"
    },
    "name": "start_free"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesYour human's own email address (throwaway services are refused).
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / email / description
      Previous value: -"Your human's email address."New value: +"Your human's own email address (throwaway services are refused)."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "email": "human@example.com"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Goes well past the annotations (openWorldHint, non-idempotent, non-destructive): it discloses that one email may be sent, that the result is identical whether or not an email goes out, the once-per-inbox/30-day limits, and that the pairing_code must be shown only in chat. The only gap is that it doesn't clarify what happens if the address has already claimed the offer, though 'the answer is the same whether an email goes out or not' covers most of it.

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?

Front-loads eligibility and the action, then walks the flow in order (give email → get code → show to human → they confirm), with the top_up alternative closing it. Dense but nearly every clause carries operational information; the parenthetical credit details could be trimmed slightly.

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

Completeness5/5

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

No output schema exists, and the description compensates by naming the returned pairing_code and describing the full downstream handshake with the human. For a two-parameter enrollment tool with openWorldHint, everything an agent needs to call it correctly and safely is present.

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% and the schema already describes both email (own address, throwaway refused) and passport_token (fallback when no app sign-in), so the description adds little parameter-level meaning. It does surface the return artifact (pairing_code), which is useful since there is no output schema, but that is flow rather than parameter semantics. Baseline 3 applies.

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?

States a specific action (ask for a free start), names the exact object ($5 starter credit, 30 days, once per inbox) and scopes it to 'a passport without an owner', then names the sibling handling the opposite case (top_up). An agent can select this over create_passport/top_up without opening any schema.

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?

Explicit when: passport without an owner, human has an email address. Explicit when-not/alternative: 'a passport with an owner uses top_up instead', and starter_status is named for after the human presses Yes. Includes a precondition (buying with the credit still needs a human yes) that prevents misuse.

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.