Skip to main content
Glama

verantis-mcp

by io.github.m9labs-railscope

get_service

Read-only

Full unified record for one service host: every settlement rail it accepts on, each with its own reputation, price, buyers, volume and history, plus coming-soon chains. Each rail's 'wallet_scope' marks a 'shared' pay-to wallet (buyers/volume are pooled inbound across 'wallet_services' services, not this one alone) vs 'dedicated' (this service's own). Pass the host (domain).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesthe service host / domain to look up, e.g. api.nansen.ai

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / domain / description
      Added value: +"the service host / domain to look up, e.g. api.nansen.ai"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds valuable behavioral context beyond that: the wallet_scope distinction between 'shared' pooled-inbound wallets and 'dedicated' wallets. No behavior contradicts 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 three sentences are front-loaded with the core purpose and then add necessary semantic detail about wallet_scope. No sentence is wasted, and the length is appropriate for the conceptual nuance being conveyed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description fully characterizes what the returned 'full unified record' contains, including per-rail fields and the subtle wallet_scope behavior. With one well-documented parameter and read-only annotations, nothing essential is missing for correct invocation.

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%, and the schema already documents 'domain' as the service host/domain to look up with an example. The description only repeats 'Pass the host (domain)', adding no new parameter-level meaning beyond what the schema provides.

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 states a specific resource ('full unified record for one service host') and enumerates its contents: settlement rails, reputation, price, buyers, volume, history, and coming-soon chains. This clearly distinguishes it from directory-level or wallet-level sibling tools, even without naming them.

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 gives clear context for use: when you need a complete record for one service host, and it explicitly instructs the caller to pass the host domain. It does not explicitly name alternatives or state when not to use this tool, but the singular-host scope is enough to guide selection.

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

All verantis-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct purpose: checking a specific wallet, searching the service directory, retrieving a full service record, and viewing index stats. There is no overlap or ambiguity; an agent can easily choose the right tool based on the task.

Naming Consistency4/5

Most tools follow the verb_noun pattern (check_wallet, find_paid_service, get_service), but directory_stats is a noun_noun which breaks the convention slightly. This is a minor deviation and the names remain clear and predictable.

Tool Count5/5

With only 4 tools, the server is tightly scoped to its purpose of verifying wallets and querying service directory information. Each tool earns its place, and the count is well within the ideal 3-15 range for a focused server.

Completeness5/5

The tool surface covers all essential operations for a read-only directory and reputation service: searching, retrieving details, checking a specific wallet, and getting summary stats. There are no obvious dead ends or missing actions within the stated domain.

Resources