Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
newdb_check_passport_mvdB

Check Russian internal passport validity via official MVD registry database.

newdb_check_fsspA

Check open enforcement proceedings, debts, and fines for a person via FSSP registry.

newdb_check_egrulA

Get full legal entity data, founders, director, authorized capital, status from EGRUL and Transparent Business (FNS).

newdb_check_fns_blockA

Check bank account suspension decisions by Russian Federal Tax Service (FNS BIKP).

newdb_check_bankrotB

Check bankruptcy records for physical persons or legal entities in Fedresurs (EFRSB).

newdb_complex_check_personB

Comprehensive background check for Russian citizen by passport (aggregates FNS INN, MVD passport, FSSP debts, bankruptcy, courts, pledge).

newdb_complex_check_companyA

Comprehensive background check for legal entity by INN (aggregates EGRUL, FNS account blocks, arbitration courts, bankruptcy, FSSP debts).

newdb_get_balanceA

Check current remaining request balance on NewDB API token.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 8 tools

Disambiguation4/5

Most tools target distinct registries: bankruptcy, passport, FSSP, EGRUL, and FNS block checking are clearly scoped. The two complex_check tools intentionally overlap these simple checks, but their names and descriptions make the aggregation purpose obvious, so an agent should rarely select the wrong one.

Naming Consistency5/5

All tools follow a consistent `newdb_<verb>_<target>` pattern, using `check_` for registry lookups and `get_` only for the plainly different balance operation. Prefixes and underscore separators are uniform, making the tool names predictable and easy to navigate.

Tool Count5/5

Eight tools is a well-scoped set for a registry-checking server: enough specific checks to cover major resources without overwhelming an agent. Each tool earns its place, especially the two aggregate checks that reduce the need to invoke many simple checks manually.

Completeness4/5

The set covers the core domain well: person checks, legal entity checks, debt/bankruptcy/account-block checks, and an aggregate version for each side. It is missing some standalone variants such as a direct court-case-only check or simple INN lookup, but those are bundled into the complex checks, so the main workflows are still supported.

Maintenance

ActivitySlowing
ResponsivenessNo issues