Skip to main content
Glama
Sign In
learn_mcp

learn_mcp

by tusharkotlapure
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_customer_balance

Retrieve a customer's current balance by providing their customer ID. Resolve balance inquiries with accurate, up-to-date data.

Instructions

Get the current balance of a customer.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "customer_id": "<customer_id>"
    },
    "name": "get_customer_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
customer_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

The word 'get' implies a read-only operation, but the description does not explicitly disclose side effects, error behavior (e.g., customer not found), or output format. With no annotations, the description carries the full burden and only partially covers transparency.

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 concise sentence with no redundancy or unnecessary details. It efficiently conveys the core functionality without fluff.

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 simple getter, the description provides enough context to understand the primary purpose. However, it does not mention potential error cases, return value specifics, or interaction with sibling tools, leaving minor gaps in completeness.

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

Parameters2/5

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

The only parameter, customer_id, is self-explanatory by name, but the schema description coverage is 0%, and the tool description adds no clarifying details about its meaning, constraints, or typical usage. Since coverage is low, the description should have compensated but did not.

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 clearly states the tool's purpose: retrieving a customer's balance. It distinguishes from sibling tools like get_customer and find_customer by focusing specifically on balance retrieval, making the action unambiguous.

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?

The description does not explicitly explain when to use this tool versus the sibling tools. While the purpose is clear, it lacks guidance on scenarios where this tool is preferred over alternatives, such as when only balance is needed rather than full customer details.

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