Skip to main content
Glama
lindoai

mcp-lindoai

Official

get_credits

Read-only

Retrieve your current workspace credit balance to track usage and plan AI content creation.

Instructions

Get workspace credit balance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'get_credits' tool via server.tool().
    server.tool(
      "get_credits",
      "Get workspace credit balance.",
      {},
      { title: "Get Workspace Credits", readOnlyHint: true, destructiveHint: false, openWorldHint: false },
      async () => {
        const data = await apiCall("/v1/ai/credits", "GET");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Handler function for 'get_credits' - calls GET /v1/ai/credits API and returns the balance.
    async () => {
      const data = await apiCall("/v1/ai/credits", "GET");
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • Schema for 'get_credits' - empty object (no input parameters).
    {},
  • Helper function apiCall() used by the handler to make authenticated HTTP requests.
    async function apiCall(path, method, body) {
      const url = `${BASE_URL}${path}`;
      const res = await fetch(url, {
        method,
        headers: {
          Authorization: `Bearer ${API_KEY}`,
          "Content-Type": "application/json",
        },
        ...(body ? { body: JSON.stringify(body) } : {}),
      });
      return res.json();
    }
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds no extra behavioral context (e.g., what happens if no workspace, or return format), which is acceptable but does not enhance transparency beyond annotations.

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?

Single sentence, no wasted words. Every part of the description is relevant 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?

Tool is simple with no parameters and annotations present. Lacks output schema or description of return value, but for a credit balance retrieval, the missing detail is minor. Overall adequate.

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 (0 params), so baseline score of 4 applies. Description does not need to add parameter info.

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?

The description 'Get workspace credit balance' clearly states the action (get) and the resource (workspace credit balance), distinguishing it from sibling tools like 'get_client_credits' which target a different scope.

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?

No guidance on when to use this tool versus alternatives (e.g., 'get_client_credits' or 'allocate_credits'), but usage is implied for retrieving workspace-level credit balance.

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

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