Skip to main content
Glama

aui_claim_free_trial

Autonomously provision a free 100-credit AUI trial key ('trial-...') using a BYOK Google Gemini API key ('AIza...'). No human signup or browser verification required.

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

Input Schema

NameRequiredDescriptionDefault
gemini_keyYesValid Google Gemini API key starting with AIza...
project_nameNoName of the agent or application.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose meaningful behavior, namely that provisioning is autonomous and requires 'no human signup or browser verification', which is genuinely useful for planning. It omits what happens to the supplied BYOK Gemini key, whether trials are limited per agent, and what a failure looks like.

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 tight sentences, front-loaded with the action and the credit amount, followed by the autonomy guarantee. Every phrase carries information and nothing is padded.

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?

There is no output schema, so the description should cover the return value; it only hints at it via the 'trial-...' prefix. For a credential-provisioning tool with side effects on an externally supplied API key, the absence of any note on key handling, error modes, or trial limits leaves a real gap.

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 both parameters are already documented and the baseline is 3. The description reinforces the Gemini key format and implies the trial key is returned, but adds no meaning about 'project_name' or how it influences the provisioned key.

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?

The description states a specific verb and resource: 'provision a free 100-credit AUI trial key'. It even pins down the output shape ('trial-...') and input shape ('AIza...'), which no other sibling name implies. It stops short of a 5 because it never explicitly positions itself against the listed siblings.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer that this is the tool to call when it needs a free trial key and happens to have a Gemini key. There is no explicit when-not guidance, no mention of alternatives, and no stated prerequisites beyond holding a valid Gemini key.

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.

Resources