Skip to main content
Glama
Sign In

ToolRouter

by io.github.Humanleap
OverviewDiscussionsAdmin

Account Preferences

account_preferences
Idempotent

Read or write billing preferences (auto-reload, budget cap, default context). Pass action: "get" to read, action: "set" with fields to write.

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": {
      "action": "<action>"
    },
    "name": "account_preferences"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes"get" to read preferences, "set" to update them.
budget_limitNoMonthly spending cap in USD, or null to remove (set only).
auto_reload_amountNoAmount (USD) to reload when triggered (set only, max 500).
auto_reload_enabledNoEnable or disable auto-reload (set only).
auto_reload_thresholdNoBalance threshold (USD) that triggers a reload (set only).
default_billing_contextNoDefault account to bill (set only). "personal" or "team:<id>".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that write mode requires supplying fields, but says nothing about auth/permission needs or what a read returns. Adequate but thin given the lower bar annotations set.

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?

Two compact sentences with the core purpose front-loaded and the mode-selection instruction second. Every sentence earns its place, though the action guidance mildly restates the schema.

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?

With no output schema, the description could say more about the return shape of a read, but the dual-mode semantics and full param documentation leave little an agent is missing. Annotations carry the safety profile, so overall coverage is solid.

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 the schema fully documents all six parameters including the set-only fields and the enum. The description's mention of action values and field categories adds little beyond what the schema already provides, so the baseline 3 applies.

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?

States a specific verb (read or write) and resource (billing preferences), and enumerates the fields covered (auto-reload, budget cap, default context). The purpose is unambiguous, though it makes no reference to any sibling tool to differentiate itself.

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?

It explains how to invoke each mode via the action parameter ("get" to read, "set" with fields to write), which implies usage. However it offers no when-not guidance, prerequisites, or alternatives among the account_* siblings.

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

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