Skip to main content
Glama
Sign In

Comunicate.top

by top.comunicate
OverviewDiscussionsAdmin

Sold

get_balance
Read-onlyIdempotent

Creditele disponibile pe fiecare pachet și soldul în bani (cenți, fără TVA).

Use when the user asks about credits, subscriptions or money left, or before ordering. Do not use without an account.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
moneyNoobject {availableCents, currency}. Money balance, in bani (1/100 leu).
creditsNoarray of {packageName, available, total}. Package credits (1 credit = 1 publication).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "credits": {
+      "description": "array of {packageName, available, total}. Package credits (1 credit = 1 publication)."
+    },
+    "money": {
+      "description": "object {availableCents, currency}. Money balance, in bani (1/100 leu)."
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds useful context beyond that: the balance is expressed in cents and excludes VAT, and an account is a hard prerequisite. It says nothing about freshness, caching, or whether package credits and money are always both present, so it is value-adding but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, with the resource statement first and the usage rule second. Every sentence carries information, though switching languages mid-description adds minor friction without adding content.

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-only tool with a full output schema and complete annotations, the description covers purpose, trigger conditions, prerequisite and output units. The remaining gap is minor: it does not indicate whether values are real-time or cached, which an agent might care about right before ordering.

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 takes no parameters, so there is no per-parameter semantics for the description to carry and the baseline applies. The description correctly spends no words on inputs and instead clarifies the output units (cents, no VAT), which is the relevant semantic detail for a zero-argument tool.

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 names the two concrete resources returned: available credits per package and the monetary balance (in cents, excluding VAT). That is a specific resource statement, though the retrieval verb is implied rather than stated and the mixed Romanian/English phrasing slows parsing slightly. It does not explicitly contrast with siblings such as plan_budget or report_summary, keeping it at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit triggers — user asks about credits, subscriptions or money left, or the agent is about to place an order — plus a negative condition: do not use without an account. That is real when/when-not guidance. It falls short of 5 because no alternative tool is named for overlapping needs (e.g. budget planning or stats), leaving the agent to infer divergence.

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

All Comunicate.top toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources