Tasvr

Set or lower this connection's spending limit

set_spend_limit

Idempotent

Sets a cap on what this connection may spend: at most credits per day, week, month or in total. An existing limit can only be lowered within its period; raising or removing it is done in TASVR Settings. Spends nothing.

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": {
      "credits": "<credits>",
      "period": "<period>"
    },
    "name": "set_spend_limit"
  }
}

Input Schema

Name	Required	Description	Default
`period`	Yes	'day', 'week', 'month', or 'total' (all spending from now on).
`credits`	Yes	The most credits this connection may spend in the period.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`message`	Yes
`spendLimit`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already mark this as a non-read-only but non-destructive, idempotent mutation; the description adds genuinely new context: the limit can only be lowered, upward changes are out of band, and the call itself spends nothing. It does not say what happens if you attempt to raise a limit or lower below already-spent credits, which is the main remaining gap.

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, front-loaded with the core action and immediately followed by the restriction. Every clause carries information; nothing is redundant padding.

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 two-parameter mutation with an output schema, the description covers purpose, restriction, out-of-band alternative, and side-effect profile. Only failure behavior when attempting to raise or lower below current spend is unexplained.

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% and both parameters are documented, including the period enum and credit bounds. The description restates the same semantics ("at most credits per day, week, month or in total") without adding format or edge-case detail, so 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?

States a specific verb and resource ("Sets a cap on what this connection may spend") plus the unit and period scope. It is clearly distinguishable from siblings like get_credits_remaining or estimate_cost, which read or project rather than set a cap.

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?

Explicitly explains the key constraint: an existing limit can only be lowered within its period, and raising or removing it must be done in TASVR Settings. That routes the agent away from futile calls. It doesn't compare against the other credit-related siblings, but the when/when-not guidance is clear.

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

All Tasvr tools Inspect

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

Need Help?