Skip to main content
Glama

Spoken

by io.github.spokenmd
OverviewDiscussionsAdmin

Get credit balance

get_balance
Read-onlyIdempotent

Check the current Spoken credit balance, account email, and recent usage for the configured API key. Does not consume credits.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
emailNoAccount email, when one is attached to the key.
usageYes
creditsYesCredits remaining; one is spent per first fetch of an episode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "credits": {
+      "description": "Credits remaining; one is spent per first fetch of an episode.",
+      "type": "number"
+    },
+    "email": {
+      "description": "Account email, when one is attached to the key.",
+      "type": "string"
+    },
+    "usage": {
+      "additionalProperties": false,
+      "properties": {
+        "recent": {
+          "description": "The 50 most recent fetches.",
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "accessedAt": {
+                "type": "string"
+              },
+              "episodeId": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "episodeId",
+              "accessedAt"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "total": {
+          "description": "Episodes fetched with this key.",
+          "type": "number"
+        }
+      },
+      "required": [
+        "total",
+        "recent"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "credits",
+    "usage"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered without the description. The description adds genuinely new behavioral context not present in annotations: 'Does not consume credits,' which is the key cost concern for a metered API. It stops short of stating auth requirements or rate limits.

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?

Two sentences, no filler. The scope of returned data is front-loaded and the cost caveat is placed where it will be read before invocation.

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?

For a no-parameter read tool with an output schema already defining the return shape, the description supplies everything an agent needs: what it returns, that it targets the configured API key, and that it is free. Return-value detail is correctly delegated to the output schema.

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 zero parameters, so there is nothing for the description to disambiguate — baseline 4 applies. The description correctly does not invent parameter guidance where none is needed.

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?

States a specific verb ('Check') and names the exact resources returned: credit balance, account email, and recent usage. It is unmistakably distinct from the podcast-management siblings (list_episodes, search_podcasts, follow_podcast), so an agent can route without opening any schema.

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 purpose (check balance before making calls), and 'for the configured API key' clarifies the scope, but there is no explicit when-to-use/when-not guidance or named alternative. Adequate for a zero-parameter read tool, but no routing instructions are given.

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

All Spoken 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