Skip to main content
Glama

Get the account trial

account_trial_get
Read-onlyIdempotent

[read-only] The connected account's trial: which one it is on (current.label, e.g. the 14-day posting trial, a plan trial or a comped plan), the day and days left, the end date, what it falls back to (current.fallsBackTo) and what happens at the end (current.after). posts.heldCount / heldPosts: booked posts held after a trial ended; they are never deleted and post again once the plan includes posting, with no re-booking. terms are the configured trial terms. (Wraps GET /api/v2/account/trial.)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the '[read-only]' prefix merely restates that. The real added value is behavioral: held posts are never deleted and re-post automatically once the plan includes posting, with no re-booking, and the description discloses what the trial falls back to and what happens at the end — context an agent cannot get from the schema.

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?

Content is front-loaded with the identity of the resource, then branches into the held-posts behavior and `terms`, with the underlying endpoint in a trailing parenthetical. It is dense and field-name-heavy but each sentence carries information; only the redundant '[read-only]' marker fails to earn its place.

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?

With no output schema, the description bears full responsibility for explaining the response, and it does so thoroughly: trial identity, remaining days, end date, fallback, post-trial outcome, held posts and configured terms. For a zero-parameter read this leaves no meaningful gap an agent would need filled.

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 no parameters, so the baseline is 4. The description spends its space on documenting return-field meaning (`fallsBackTo`, `after`, `heldCount`) instead of inventing parameter guidance, which is the right allocation.

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 names the exact resource (the connected account's trial) and enumerates the concrete payload fields — `current.label`, days left, end date, `current.fallsBackTo`, `current.after`, `posts.heldCount`/`heldPosts`, `terms` — so an agent knows precisely what it retrieves. It does not explicitly contrast itself with nearby `account_*` siblings, which keeps it at a 4 rather than a 5.

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?

There is no explicit when-to-use statement or exclusion clause; guidance is only implied by a zero-argument getter whose purpose is self-evident. A reader can infer 'call this to inspect the trial state, fallback plan and any held posts,' but the definition never says so directly or points at an alternative.

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