Skip to main content
Glama
milligold-mcp

milligold-mcp

by sepehr071

Milli.gold help topics

mg_help_topics
Read-onlyIdempotent

Search Milli.gold help-center articles by English keyword to find guides on buying, selling, delivery, transfers, verification, and fees, then read the matching article.

Instructions

Find Milli.gold help-center articles (how to buy, sell, deliver, transfer, verify, fees) by English keyword.

About 80 Persian articles with English URLs, so match on English words. Read one with mg_read.

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_help_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoEnglish keywords matched against article URLs, e.g. 'delivery'. Empty = all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedInput schema / properties / query / description
      Previous value: -"English keywords matched against help article URLs, e.g. 'delivery', 'fee', 'card'. Empty = all."New value: +"English keywords matched against article URLs, e.g. 'delivery'. Empty = all."
  2. Addedv0.2.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered; the description adds the non-obvious corpus quirk (≈80 Persian articles exposed under English URLs) that materially affects query construction. It does not describe the shape of returned results, which is the 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, front-loaded with purpose and followed by the operational caveat and the handoff to mg_read. No filler or repetition of schema fields.

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, zero-required read tool with full schema coverage and rich annotations, this is nearly sufficient. The one omission is what a hit looks like (title only? URL? snippet?), which would help an agent decide when to escalate to mg_read.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: the query must be an English keyword because matching happens against English URLs on otherwise Persian content, explaining why the parameter is language-constrained. That rationale is not present in the schema text.

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 ('Find Milli.gold help-center articles'), enumerates the topic space (buy, sell, deliver, transfer, verify, fees), and explicitly positions the sibling mg_read as the follow-up step. An agent can distinguish this from mg_read and the data-oriented siblings without opening either schema.

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 concrete operating guidance: search by English keyword, and use mg_read to read a specific article. The Persian-article/English-URL caveat tells the agent how to phrase queries effectively. It lacks an explicit 'do not use for X' exclusion, but the routing instruction to mg_read covers the main adjacency.

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