Skip to main content
Glama

Start a trial without login

create_trial_access

Create a private 24-hour trial token automatically. No ChatGPT account, payment or manual setup. Audio: 3 jobs per session. Chat/images: shared queue of 3 active tasks, no per-session job quota. Global access issuance caps apply. Retain the token for upload and result retrieval. Reuse the session; never create new sessions to bypass quotas.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_trial_access"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare the non-read-only, non-idempotent, non-destructive profile; the description adds real behavioral detail the annotations cannot convey — 24-hour expiry, the 3-audio-jobs-per-session limit, the shared 3-active-task queue for chat/images, and global issuance caps. It stops short of saying what repeated calls do (whether each call mints a fresh session that consumes global cap) or what the response contains, which matters given idempotentHint=false.

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-loaded with the action and its headline constraints (24h, private, automatic), then quotas, then the retention warning. Dense but effective; the telegraphic fragments ('No ChatGPT account, payment or manual setup') are slightly clipped rather than fully formed.

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 should ideally say that a token is returned and how to feed it to the submit_* siblings — it only implies this via 'Retain the token for upload and result retrieval.' Quotas, expiry and misuse constraints are otherwise well covered for a zero-parameter tool.

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

Parameters4/5

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

Zero parameters, so there is nothing to disambiguate and the baseline applies. The description correctly spends no words on parameter syntax.

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 ('Create a private 24-hour trial token') plus the defining scope: no account, no payment, 24-hour lifetime. None of the sibling tools (get_*/submit_*) issue tokens, so the boundary is unambiguous.

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

Usage Guidelines4/5

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

Makes the entry condition clear (no login required) and gives an explicit anti-pattern: 'Reuse the session; never create new sessions to bypass quotas.' It does not name a competing tool to use instead, but no sibling offers an equivalent capability, so the guidance is sufficient without exclusions.

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