Skip to main content
Glama
Sign In
Zearch MCP

Zearch MCP

Official
by zearchcomputer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Credit balance

get_wallet
Read-onlyIdempotent

Show the Zearch credit balance for the current key, including available and held credits, plan, lot expiration, and optional recent ledger entries.

Instructions

Show the Zearch credit balance this key spends from: available and held credits, plan, credit lots and when they expire. Optionally include recent ledger entries. Free.

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_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
beforeNonext_before cursor from a previous call, for older entries.
include_entriesNoAlso return recent ledger entries.

Output Schema

NameRequiredDescriptionDefault
walletYes
entriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish that this is read-only, idempotent, non-destructive, and closed-world. The description adds relevant behavioral context beyond annotations: it is free, scoped to the current key, and reports available versus held credits along with plan and expiration data. It does not cover pagination or auth expectations, but the output schema and parameter descriptions carry that burden.

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 two short sentences with the core purpose front-loaded. Every clause adds meaningful detail about scope, returned balance components, optional entries, or cost, with no wasted wording.

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

Completeness5/5

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

Given the low complexity, rich annotations, complete parameter schema, and existing output schema, the description is complete for correct invocation. It identifies the resource, what is returned, the optional ledger expansion, and the fact that the call is free.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters thoroughly. The description adds only that ledger entries can be included optionally, which maps to include_entries and does not explain the before cursor. This is appropriately at the baseline because the schema does the detailed work.

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 gives a specific verb and resource: show the Zearch credit balance for the current key. It also enumerates what the balance includes, such as available and held credits, plan, credit lots, and expiration. It does not explicitly differentiate itself from sibling tools like get_pricing, so it stops short of a 5.

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 implied by the phrase 'this key spends from' and the optional ledger entries, suggesting this is a balance-checking tool. However, there is no explicit when-to-use guidance, no exclusion of alternatives such as get_pricing, and no statement about when ledger entries are worth including.

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