Skip to main content
Glama

storyshort_get_usage_stats

Retrieve credit balance, API call counts (today and total), and recent credit transactions to monitor StoryShort API usage.

Instructions

Get API usage statistics: credit balance, API call counts (today/total), and recent credit transactions.

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_usage_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and does not discharge it. It does not state that this is a read-only, side-effect-free call, nor whether it requires an authenticated account, how far back 'recent' transactions go, whether results are paginated or capped, or what the timezone/scope of 'today' is.

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 a colon-delimited list of returned fields; every clause adds information and there is no filler or redundancy.

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 annotations and no output schema, the enumerated return contents effectively substitute for a return-value description. The remaining gaps are the vague 'recent' window and the undefined 'total' scope, which leave an agent guessing at the shape of results.

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 description correctly implies the tool needs no inputs, and there is nothing parameter-related left to document.

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 uses a specific verb (Get) and resource (API usage statistics) and enumerates the returned contents: credit balance, API call counts today/total, and recent credit transactions. That makes the tool's function unambiguous, but it never distinguishes itself from sibling storyshort_get_credit_balance, whose name suggests overlapping output.

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 this is the broad usage/accounting view and that storyshort_get_credit_balance is the narrower one, but no explicit when-to-use or when-not-to-use statement is given. There is no mention of prerequisites such as authentication or API-key scope.

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