Skip to main content
Glama
Sign In
seven-mcp

seven-mcp

Official
by seven-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_subaccount

Configure automatic balance transfers for a subaccount by setting a credit threshold and transfer amount in EUR.

Instructions

Configure automatic balance transfer for a subaccount

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

Input Schema

NameRequiredDescriptionDefault
idYesSubaccount ID
thresholdYesCredit threshold below which credit should be transferred (in EUR)
amountYesAmount of credit to transfer from main account (in EUR)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states the action without explaining side effects, idempotency, or whether existing settings are replaced or appended.

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?

A single, focused sentence with no unnecessary words. Every phrase serves a purpose.

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 simple tool with 3 parameters and no output schema, the description is adequate but lacks details on behavior (e.g., whether this is a create-or-update operation).

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 coverage is 100%, so the description does not need to add much meaning. The description aligns with parameters but adds no extra context beyond the schema.

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 description 'Configure automatic balance transfer for a subaccount' uses a specific verb ('configure') and resource ('automatic balance transfer for a subaccount'), clearly distinguishing it from sibling tools like 'create_subaccount' and 'transfer_credits'.

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?

No guidance on when to use this tool versus alternatives (e.g., 'transfer_credits' for manual transfers). No prerequisites or context are provided.

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

Deploy Server

Other Tools