Skip to main content
Glama
sparebank1-mcp

sparebank1-mcp

by MrLightful

List child accounts

sb1_list_child_accounts
Read-onlyIdempotent

Retrieves accounts for a known child ID so callers can review balances and account details; it does not discover or resolve child IDs.

Instructions

List accounts for an exact child ID already known to the caller. This API does not provide child-ID discovery.

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": {
      "childId": "<childId>"
    },
    "name": "sb1_list_child_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
childIdYes

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already establish read-only, idempotent, non-destructive behavior. The description adds a relevant capability limitation that child-ID discovery is not supported, but it does not cover return behavior, pagination, or other operational details beyond the annotations.

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?

The description is two tight sentences with no filler. The key requirement is front-loaded, and the limitation follows immediately.

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 single-parameter list tool with an output schema and rich annotations, the description covers the essential prerequisite and the main non-discovery limitation. It could still say more about the nature of child accounts or how the caller should have obtained the child ID.

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 description must carry parameter meaning. It usefully clarifies that childId must be an exact known ID rather than a search term, but it does not explain the expected format, source of the ID, or other semantics beyond the schema's pattern and length constraints.

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 uses a specific verb and resource: list accounts for a child ID. It adds a useful scope constraint by saying the child ID must already be known, which helps distinguish it from broad account-listing behavior, though it does not explicitly name the sibling sb1_list_accounts.

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?

It clearly states when to use the tool: when an exact child ID is already known. It also states when not to use it for discovery, but does not name any alternative tool for obtaining a child ID.

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