Skip to main content
Glama
Fewsats

Fewsats MCP Server

Official
by Fewsats
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

billing_info

Retrieve billing and shipping details for secure payment processing within the Fewsats MCP Server.

Instructions

Retrieve the user's billing information. Returns billing details including name, address, and other relevant information. This information can also be used as shipping address for purchases.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/fewsats_mcp/server.py:58-63 (handler)
    The handler function for the 'billing_info' MCP tool. It is decorated with @mcp.tool() which registers it with the MCP server. The function calls Fewsats().billing_info() to fetch the billing information and uses handle_response to format the API response.
    @mcp.tool()
async def billing_info() -> str:
    """Retrieve the user's billing information.
    Returns billing details including name, address, and other relevant information.
    This information can also be used as shipping address for purchases."""
    return handle_response(Fewsats().billing_info())
  • src/fewsats_mcp/server.py:9-11 (helper)
    Helper function used by billing_info (and other tools) to handle HTTP responses from the Fewsats API, returning status code and parsed JSON or text.
    def handle_response(response):
    try: return response.status_code, response.json()
    except: return response.status_code, response.text
  • src/fewsats_mcp/server.py:58-58 (registration)
    The @mcp.tool() decorator registers the billing_info function as an MCP tool.
    @mcp.tool()

Tool Definition Quality

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a retrieval operation (implying read-only) and hints at the return content (billing details), but doesn't cover aspects like authentication needs, rate limits, or error handling. This is adequate but has clear gaps for a tool with zero annotation coverage.

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?

The description is concise and well-structured with three sentences that each add value: stating the purpose, detailing the return, and providing usage context. It's front-loaded with the core function, though the third sentence could be slightly more integrated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is reasonably complete for a retrieval operation. However, it lacks details on the return format (e.g., structure of billing details) and doesn't address potential errors or edge cases, which could be helpful for an agent.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a high baseline score. It could be a 5 if it explicitly noted the lack of parameters, but this is minor.

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 clearly states the tool's purpose with a specific verb ('Retrieve') and resource ('user's billing information'), making it immediately understandable. However, it doesn't explicitly differentiate this from sibling tools like 'payment_info' or 'payment_methods', which prevents a perfect score.

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?

The description implies usage context by mentioning that the information can be used as a shipping address for purchases, which suggests when this tool might be relevant. However, it lacks explicit guidance on when to use this versus alternatives like 'payment_info' or 'balance', leaving some ambiguity for the agent.

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/Fewsats/fewsats-mcp'

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