Skip to main content
Glama

storyshort_get_subscription

Retrieve your subscription plan, status, video limits, and credit allocation to verify current usage and available limits.

Instructions

Check your subscription plan, status, video limits, and credit allocation.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden; 'Check' implies a safe read but never states it explicitly, nor whether it applies to the authenticated account only, what happens when no subscription exists, or auth requirements. It does add value by enumerating the four data categories returned (plan, status, video limits, credit allocation), which is real disclosure beyond the empty schema.

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?

A single front-loaded sentence with no filler; the resource categories arrive immediately. Nothing could be removed without losing meaning.

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 tool with no output schema, the description usefully enumerates the return fields, which compensates for the missing output schema. Minor gaps remain around scope (whose subscription) and error/no-subscription behavior, but nothing that would block a correct call.

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 no parameter semantics to explain and the baseline of 4 applies. Nothing in the description conflicts with the empty input schema.

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?

States a specific verb ('Check') and a concrete resource set (subscription plan, status, video limits, credit allocation), so an agent knows exactly what data this returns. It does not explicitly distinguish itself from siblings like storyshort_get_credit_balance or storyshort_get_usage_stats, which overlap on the credit/limits portion.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance, and no mention of the closely related credit-balance and usage-stats siblings. The agent must infer from the name alone that this is the account/plan-level lookup rather than the more granular ones.

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