Skip to main content
Glama
Sign In
Yugo MCP Server

Yugo MCP Server

by georgi-shulev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

get_accounts

Retrieve a paginated list of accounts with their balances, filtered by currency as needed.

Instructions

List Accounts — Retrieve a paginated list of accounts with their balances — [GET /accounts]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number to retrieve (1-based indexing)
currencyNoFilter results by currency code
page_sizeNoMaximum number of items to return per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses the HTTP method (GET), pagination behavior, and that balances are included. However, it does not mention authentication requirements, error handling, or rate limits, so some transparency gaps remain.

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 a single, front-loaded sentence with a clear structure: tool name, brief description, and endpoint reference. It contains no unnecessary words and is immediately scannable.

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?

Given the tool's simplicity (3 optional params, no output schema), the description provides sufficient context for core functionality: it lists accounts with pagination and balances. It does not explain return value specifics, but for a list operation this is acceptable, especially without an output schema.

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?

The schema has 100% description coverage for all three parameters (page, currency, page_size), so the description does not need to add parameter-level details. The description's mention of pagination adds no extra meaning beyond what the schema already documents.

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 clearly states the tool 'List Accounts' and specifies 'Retrieve a paginated list of accounts with their balances', using a specific verb and resource. It distinguishes from sibling tools like get_payins and get_payouts by focusing on accounts.

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

Usage Guidelines3/5

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

Usage context is implied by the tool name and resource type, but there is no explicit guidance on when to use this tool versus alternatives. The sibling tools are distinct enough that misuse is unlikely, but the description does not provide any when-to-use or when-not-to-use instructions.

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