Skip to main content
Glama

HokuHost Domains

setup_card

Returns setup_url where the owner saves a card once, with a monthly limit; orders are then paid automatically within it. A lower limit for a saved card applies at once.

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": {
      "monthly_limit_usd": "<monthly_limit_usd>"
    },
    "name": "setup_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthly_limit_usdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the agent knows this is a mutating, externally-facing call. The description adds genuinely useful behavior beyond that: the card is saved once, subsequent orders auto-charge against the limit, and a lowered limit takes effect immediately. It does not say what state the tool itself creates server-side, whether the setup_url expires, or what happens when the monthly limit is reached.

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 short sentences with the primary return value (setup_url) front-loaded and no filler. The second sentence's wording ('within it') is slightly muddy, but nothing is redundant or padded.

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?

With no output schema, the description correctly covers the key return value and the recurring-payment semantics. However, for an open-world mutating tool it omits the auth/ownership requirements, the lifecycle of the returned URL, and limit-exceeded behavior, leaving real gaps an agent would want before calling it.

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 0%, so the schema gives only a name, type, and 1–2000 range with no stated unit. The description partially compensates by framing the value as a monthly limit and noting that a lower limit applies at once, implying a recurring spending cap, but it never states the currency or whether exceeding the cap blocks or queues orders.

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 names a concrete verb and output (returns setup_url) plus the resource being configured (a saved card with a monthly limit) and the downstream effect (orders paid automatically). It is understandable what the tool accomplishes, though the phrasing 'paid automatically within it' is ambiguous about whether 'it' refers to the limit or the card, and no sibling tool is named for contrast.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no statement of prerequisites (e.g., whether the owner must already exist or be signed in), and no mention of alternatives such as create_order for one-off payments. The agent must infer the setup-versus-charge workflow entirely from the description's narrative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources