Skip to main content
Glama
deenesjakoruzh
avivshafir

revenuebase-mcp-server

by avivshafir
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

new_api_key

Generate a new API key to authenticate and access Revenuebase MCP server features and data.

Instructions

Generates and returns a new API key for the user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.py:57-68 (handler)
    The complete handler function for the 'new_api_key' MCP tool, including the @mcp.tool() decorator which serves as both the implementation and registration. It makes a GET request to the Revenuebase API to generate and return a new API key.
    @mcp.tool()
def new_api_key() -> dict:
    """
    Generates and returns a new API key for the user.
    """
    if not api_key:
        raise RuntimeError("Environment variable REVENUEBASE_API_KEY is not set")
    url = "https://api.revenuebase.ai/v1/new-api-key"
    headers = {"x-key": api_key, "Accept": "application/json"}
    resp = requests.get(url, headers=headers, verify=False)
    resp.raise_for_status()
    return resp.json()

Tool Definition Quality

B3.1/5.0
Behavior2/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 mentions that it 'Generates and returns' an API key, implying a write operation, but lacks details on permissions needed, rate limits, whether the key is immediately active, or if old keys are invalidated. This leaves significant gaps for a tool that likely involves security-sensitive actions.

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?

The description is a single, clear sentence with no wasted words, making it easy to parse and understand quickly. It's appropriately sized for a simple tool with no parameters.

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

Completeness2/5

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

Given the complexity of generating an API key (a security-sensitive write operation), no annotations, and no output schema, the description is incomplete. It doesn't explain what the returned API key looks like, any associated metadata, or behavioral traits like authentication requirements, making it inadequate for safe and effective use.

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 doesn't add parameter details, which is appropriate here, but it could have mentioned if any implicit parameters (like user context) are involved. Baseline is 4 for 0 parameters.

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 action ('Generates and returns') and the resource ('a new API key for the user'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools, as none appear to be related to API key management, so it doesn't need explicit distinction.

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?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or any context about its role among the sibling tools. It simply states what it does without indicating appropriate scenarios or exclusions.

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/avivshafir/revenuebase-mcp-server'

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