get_ai_walletAI spend wallet: balance, month-to-date spend, monthly cap, auto-recharge status, and last top-up.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": false,
+ "properties": {},
+ "type": "object"
+}Input schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesAdded value: +falseDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, covering the safety profile. The description adds value by specifying the exact fields returned, which sets expectations about the output contents. No additional behavioral traits (rate limits, auth, side effects) are needed for this simple read-only tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence formatted as a concise list. Every word earns its place, with no filler or redundancy. It immediately identifies the resource and enumerates the key output components in a structured way.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (zero parameters, output schema present, annotations covering safety), the description is complete. It fully conveys what the agent can expect to receive. The sibling context of numerous get_* tools does not create ambiguity because the resource name 'AI wallet' is specific and sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, and the input schema is empty with all properties absent. Per the rubric, a baseline of 4 applies since there are no parameters to describe. The description naturally contains no parameter information, which is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns AI wallet data, enumerating five specific data points: balance, month-to-date spend, monthly cap, auto-recharge status, and last top-up. This distinguishes it from sibling tools by naming the exact resource and content, making it unambiguous which get_* tool to select.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when an agent needs AI wallet financial information, but it does not explicitly state when to use this tool versus alternatives or provide any exclusionary guidance. There is no mention of alternative tools for related budgeting queries, so the guidance remains implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct data points (e.g., get_analytics_summary vs get_brand_score). However, 'search' and 'search_catalog' have overlapping functionality and could cause confusion, and 'fetch' is a helper tied to 'search', adding minor ambiguity.
The majority use consistent verb_noun snake_case (e.g., get_inventory, list_stores). Exceptions like 'fetch' and 'search' (without object) break the pattern, but they are few.
43 tools is excessive for a data-retrieval-only API. Many get_* and search_* tools could be consolidated (e.g., search_catalog, search_inventory, search_orders are similar). The large number will overwhelm an agent.
The tool set is entirely read-only (get, search, list, fetch). There are no create, update, or delete tools, which is a critical gap for managing e-commerce operations. Agents can only view data, not act on it.