Skip to main content
Glama

Get a free machine trial

get_trial_access

Create a free trial credential without login, email, card or subscription. Three execution attempts and twenty total check/usage requests, one-hour expiry, shared service capacity limits. Failed execution attempts count. Cannot purchase or spend money. Do not repeatedly create trials to evade limits.

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": "get_trial_access"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare it is not read-only, not idempotent and not destructive, so the baseline is lower; the description still adds substantial context with concrete quotas (three execution attempts, twenty check/usage requests, one-hour expiry) and the note that failed attempts count. It omits what happens when quotas are exhausted, whether an existing credential is returned instead of a new one, and where the credential should then be used.

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 core action and limited to four dense sentences, all of which carry real constraint information. The middle sentence is a compressed, telegraphic list of limits that reads slightly run-on, and the ordering of quota rules is not grouped logically.

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?

For a zero-parameter tool with no output schema, the definition covers what is produced (a trial credential), the hard limits and expiry, and the abuse constraint. The main gap is that it never describes what the caller receives or how to use the credential afterwards, though the annotations and lack of an output schema lower that burden.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No contradictory or extraneous parameter guidance is present.

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 concrete verb and resource: it creates a free trial credential usable without login, email, card or subscription. That is enough to distinguish it from the operational siblings (get_service_info, get_usage, check_asset, prepare_check), but no sibling is named or explicitly excluded, so it falls short of the top mark.

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?

It gives clear when-to-use context (bootstrapping access without any account prerequisites) and an explicit prohibition: do not repeatedly create trials to evade limits. It stops short of naming an alternative for already-provisioned callers or describing the prerequisites for the sibling tools.

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