Skip to main content
Glama

Get subscription plan

autoshort_get_subscription
Read-onlyIdempotent

Retrieve your subscription plan, status, and credit allocation to monitor billing and available video-creation credits.

Instructions

Your subscription plan, status and credit allocation. Requires the "billing:read" scope. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description earns credit for adding two facts the annotations do not carry: the required "billing:read" scope (an auth prerequisite) and that the call is free of credit cost.

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 terse sentences, front-loaded with what is returned before the scope prerequisite. The noun-phrase opening and the dangling "Free." are slightly clipped, 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?

For a zero-parameter, read-only lookup with full annotation coverage, the description covers what comes back, the auth scope, and the cost. With no output schema, naming the three returned facets (plan, status, credit allocation) is sufficient, though a hint about the data's freshness or shape would make it airtight.

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 the baseline is 4. The empty schema leaves nothing to disambiguate, and the description correctly does not pad with parameter talk.

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?

Names the specific resource and its returned facets: subscription plan, status, and credit allocation. That partially separates it from siblings like autoshort_get_credit_balance and autoshort_get_limits, though it never explicitly states the distinction, and the fragment lacks a leading verb ("Get"/"Retrieve").

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 only implied: an agent can infer you call this to read your plan state, and "Free" hints it costs no credits. There is no explicit when-to-use guidance and no mention of when a sibling such as autoshort_get_credit_balance or autoshort_get_limits would be the better choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.