HireSquire Agent Ecosystem

enable_auto_reload

Set up automatic credit purchases when the account balance drops below a specific threshold. Use this to ensure autonomous agents never run out of credits.

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": {
      "threshold": "<threshold>",
      "amount": "<amount>",
      "payment_method_id": "<payment_method_id>"
    },
    "name": "enable_auto_reload"
  }
}

Input Schema

Name	Required	Description
`amount`	Yes	Amount to reload each time (min $5.00).
`threshold`	Yes	Balance threshold in dollars (e.g., 10.00).
`payment_method_id`	Yes	Saved Stripe payment method ID.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedMay 16, 2026

changedInput schema / properties / amount / description

Previous value: -"Amount to reload each time (in dollars, min $5)"New value: +"Amount to reload each time (min $5.00)."

changedInput schema / properties / payment_method_id / description

Previous value: -"Stripe payment method ID to use"New value: +"Saved Stripe payment method ID."

changedInput schema / properties / threshold / description

Previous value: -"Minimum balance to trigger reload (in dollars)"New value: +"Balance threshold in dollars (e.g., 10.00)."

First observedMay 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the core mechanism (recurring purchases fire when balance falls below the threshold, and the amount is charged each time), which is real value beyond the schema. It says nothing about whether this authorizes ongoing charges, how to inspect or revoke the configuration, idempotency of repeated calls, or what happens if a payment fails.

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 mechanism and followed by the motivating use case. No filler, no restatement of the tool name, and nothing that could be cut without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-required-parameter tool with no output schema, the description covers what it does and why an agent would want it. For a mutation that initiates recurring spending, however, it omits how the configuration is later viewed or revoked and what the caller gets back on success. Adequate but with clear gaps given the financial side effects.

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 minimum for amount and the Stripe payment method reference. The description only restates the threshold concept and adds no format, unit, or constraint detail beyond the structured fields. 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?

The description pairs a specific verb with a specific resource and trigger: it sets up automatic credit purchases conditioned on balance dropping below a threshold. That is far more precise than a restatement of the name. It does not explicitly name the counterpart tool disable_auto_reload, so sibling differentiation is left implicit.

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?

"Use this to ensure autonomous agents never run out of credits" gives a clear context for when to reach for this tool. There is no stated when-not condition, no mention of disable_auto_reload as the way to undo it, and no prerequisites such as needing a saved payment method first.

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

All HireSquire Agent Ecosystem 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?