Skip to main content
Glama

get_credits

Check your current credit balance and usage details for job search and application features.

Instructions

Get your current credit balance and usage information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The registration and handler implementation for the 'get_credits' tool in src/tools/job-hunts.ts. It calls the 'client.getCredits()' method to fetch credit information.
    server.tool(
      'get_credits',
      'Get your current credit balance and usage information',
      {},
      async () => {
        const result = await client.getCredits();
        const response = {
          credits: result.autoApplyQuota,
          creditsRemaining: result.autoApplyQuotaRemaining,
          message: result.autoApplyQuotaRemaining > 0
            ? `You have ${result.autoApplyQuotaRemaining} credits available for auto-apply and other operations.`
            : 'You have no credits remaining. Purchase credits to continue: https://6figr.com/jobgpt?addCreditsPopup=true',
        };
        return { content: [{ type: 'text' as const, text: JSON.stringify(response, null, 2) }] };
      }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions retrieving credit balance and usage, which implies a read-only operation, but doesn't specify authentication needs, rate limits, error conditions, or what the return format looks like (e.g., structured data, currency units). This leaves significant gaps for an agent to understand how to handle the tool effectively.

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 that directly states the tool's purpose without any fluff or redundant information. It's front-loaded and 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.

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 minimally adequate but lacks depth. It covers the basic purpose but omits details on behavior, output format, and usage context, which could hinder an agent's ability to integrate it smoothly into workflows. The absence of an output schema means the description should ideally hint at return values, but it doesn't.

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 has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description appropriately doesn't discuss parameters, which is efficient. A baseline of 4 is applied since no parameters exist, and the description doesn't need to compensate for any gaps.

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 ('Get') and resource ('your current credit balance and usage information'), making it immediately understandable. However, it doesn't distinguish this tool from any potential siblings that might also retrieve credit-related data, though none are listed among the provided sibling tools.

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 contextual constraints. It merely states what the tool does without indicating scenarios where it's appropriate or how it relates to other tools in the set.

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/6figr-com/job-gpt-mcp-server'

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