Skip to main content
Glama
milligold-mcp

milligold-mcp

by sepehr071

Milli.gold platform statistics

mg_platform_stats
Read-onlyIdempotent

Retrieve Milli.gold platform statistics—users, trades, gold traded, gold held, and branches—as rounded totals with weights in kilograms.

Instructions

Get Milli.gold's headline numbers: users, trades, gold traded, gold held and branches.

Rounded totals the company publishes; weights in kilograms.

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": "mg_platform_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the safety profile is settled. The description earns credit for going beyond them by disclosing that the figures are rounded published totals and that weights are in kilograms, which prevents misreading precision and units. It does not say how current the snapshot is, which is a minor remaining gap.

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?

Two short sentences with the metric list front-loaded and the rounding/unit caveat second. No filler, no repetition of the tool name or annotations.

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?

With no output schema, the description has to carry the return-value burden on its own, and it does so by listing every metric returned plus units and rounding. Missing only freshness or as-of date information, which an agent calling a statistics endpoint would reasonably want.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to compensate for. The unit note (kilograms) is the only semantic detail needed and it is present.

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 names a specific verb and resource ('Get Milli.gold's headline numbers') and enumerates exactly which metrics come back: users, trades, gold traded, gold held and branches. That enumeration makes it unmistakable against siblings like mg_get_price or mg_fees, which return different data.

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 is only implied: an agent can infer this is the snapshot-of-company-totals tool rather than a live price or fee lookup. There is no explicit statement of when to prefer it over mg_get_price/mg_price_history or of any prerequisite, so the guidance is adequate but not directive.

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