Skip to main content
Glama
Sign In

normi

by io.github.NormiHQ
OverviewDiscussionsAdmin

Show Credit Options

show_credit_options
Read-only

Show the user their Normi credit balance and the credit packs and plans they can buy, in an interactive view.

ONLY call this right after a Normi tool was refused with "Insufficient credits", passing that tool as refused_tool and its exact arguments as refused_arguments. Never call it otherwise, and never suggest buying credits on your own initiative.

The user buys on Normi's website in their browser; nothing is bought from this tool. Once they have added credits, the view lets them run the refused call again.

Cost: 0 credits

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": "show_credit_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNoSet by the credits view when it re-reads the balance. Leave unset.
refused_toolNoThe Normi tool that was just refused for insufficient credits.
refused_argumentsNoThe exact arguments of the refused call, so the user can run it again after adding credits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/non-destructive/non-open-world annotations, it discloses that the purchase happens on Normi's website rather than through this tool, that the view enables re-running the refused call afterwards, and that it costs 0 credits. These are exactly the behavioral facts an agent needs and none are in the annotations.

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?

Front-loaded with purpose, then the strict gating condition, then the mechanics and cost. Every sentence carries distinct operational information with no filler.

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 zero-cost interactive view with no output schema, the description covers when to call it, what it displays, where the transaction actually occurs, and the follow-up path. An agent can invoke it correctly with no further context.

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 all three parameters are already documented in the schema, including the instruction to leave 'refresh' unset. The description restates refused_tool/refused_arguments usage but adds no format or edge-case detail beyond the schema, so the baseline 3 applies.

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 first sentence states a specific verb and resource: show the user their Normi credit balance and the credit packs and plans available, in an interactive view. It is unambiguous and clearly distinct from every sibling, which are all real-estate analytics tools.

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

Usage Guidelines5/5

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

Gives the exact triggering condition (only right after a Normi tool was refused with "Insufficient credits"), names the arguments to pass, and states an explicit exclusion: never call it otherwise and never suggest buying credits on its own initiative. Nothing is left to inference.

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

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