Skip to main content
Glama
Sign In
PicoBerry MCP Server

PicoBerry MCP Server

by UModeler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_credits

Retrieves the current PicoBerry credit balance for the authenticated API key so you can check available credits before generating 3D models, images, or animations.

Instructions

Get the current PicoBerry credit balance for the authenticated key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the read-only nature ('Get') and the auth model ('authenticated key'), which prevents an agent from assuming it can query other accounts. It does not mention rate limits, whether the balance is real-time or cached, or units/currency of the returned figure.

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?

A single front-loaded sentence with no waste. Every word earns its place: the verb, the resource, the scope, and the auth context.

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?

For a zero-parameter read with no output schema, the description covers what is needed to invoke it correctly. A brief note on what the balance represents (units, currency, real-time) would fully close the gap, but the omission is minor.

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 zero parameters, so there is nothing to disambiguate and the baseline is 4. The description correctly implies no inputs are required.

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?

States a specific verb+resource ('Get the ... credit balance') and scopes it to the authenticated key. It is unambiguous against siblings like generate_image or get_asset, though it does not explicitly name what it is not.

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?

Usage is only implied — an agent can infer it should call this to check remaining credits before/after spending. There is no explicit when-to-use statement, no mention of when it might be unnecessary, and no alternatives, though no sibling covers credits.

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

Deploy Server

Other Tools