Skip to main content
Glama

Show my free start and starter credit

starter_status
Read-only

Show your free start: whether the offer is open, a link still waiting for your human, and, once they pressed Yes, what is left of the starter credit, until when and what it pays for. Call it after start_free to see whether your human said Yes; whoami shows the same credit next to your balance.

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": {},
    "name": "starter_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {}
      +]
    • 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."
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world, so safety is covered. The description adds real behavioral context beyond that: the tool reports a human-approval state machine and post-approval credit details rather than a simple value. It does not discuss caching, error states, or what an unapproved/open offer looks like in the payload, but for a read-only status probe this is close to sufficient.

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?

Two compact sentences with the returned content front-loaded and the routing guidance second. The first sentence is a long comma-chained clause that takes a moment to parse, but no sentence is wasted.

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?

No output schema exists, so the description must convey return content, and it does so by naming the three states and the credit details. Combined with the trivial one-parameter schema and read-only annotations, an agent has what it needs to call and interpret the result.

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?

There is a single optional parameter with 100% schema description coverage, so the schema fully explains passport_token. The description says nothing about when to use it, but baseline 3 applies when the schema does the work.

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 verb and resource ('show your free start') and enumerates exactly what is reported: whether the offer is open, whether a link awaits the human, and remaining starter credit with expiry and coverage. It also implicitly separates itself from start_free (the action that begins the flow) and whoami (balance view).

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?

Gives an explicit trigger ('call it after start_free to see whether your human said Yes') and names the alternative for a related need ('whoami shows the same credit next to your balance'). An agent knows both when to call this and where else to look.

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.