Skip to main content
Glama
neosapience

Typecast API MCP Server

by neosapience
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Get the authenticated user's subscription plan, credit usage, and concurrency limit

get_my_subscription

Retrieve your Typecast subscription details including plan tier, credit usage, and concurrency limit.

Instructions

Get the authenticated user's subscription information.

Calls GET /v1/users/me/subscription and returns the plan tier, credits
(used / total), and concurrency limit.

Returns:
    Dict with this shape:
        {
            "plan": "free" | "lite" | "plus" | "custom",
            "credits": {"plan_credits": int, "used_credits": int},
            "limits": {"concurrency_limit": int}
        }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

Description explains it's a GET call and returns a specific dict shape. No destructive behavior, and the verb 'get' implies read-only. Lacks explicit mention of auth or rate limits, but for a simple read tool this is sufficient.

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?

Description is 4 sentences, includes the return shape in a readable format. Could be slightly shorter, but is well-structured and front-loaded.

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?

Given zero parameters and no output schema, the description provides the return shape in detail. It covers the essential behavioral aspects for a simple get tool.

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?

No parameters exist, and schema coverage is 100%. The description adds no extra parameter info, which is appropriate since there are none to document.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Title and description clearly state that this tool retrieves the authenticated user's subscription plan, credit usage, and concurrency limit. It specifies the endpoint and return shape, and no sibling tool overlaps in purpose.

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?

Usage is implied: use when you need the current user's subscription info. No explicit when-not-to-use or alternative tools are mentioned, but the tool is self-contained and straightforward.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/neosapience/typecast-api-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server