Skip to main content
Glama
milligold-mcp

milligold-mcp

by sepehr071

Milli.gold read post

mg_read
Read-onlyIdempotent

Reads a Milli.gold news, magazine, or help post URL and returns its Persian text, with tables flattened into pipe-separated lines and an optional character limit.

Instructions

Read the text of one Milli.gold news, magazine or help post, with tables flattened to 'a | b | c' lines.

Persian text; only milli.gold news, mag and help URLs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "mg_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesmilli.gold news, mag or help post URL from mg_latest_posts or mg_help_topics.
max_charsNoCut text at this many characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • changedInput schema / properties / max_chars / description
      Previous value: -"Cut the text at this many characters (500-20000)."New value: +"Cut text at this many characters."
    • changedInput schema / properties / url / description
      Previous value: -"URL of a milli.gold news, mag or help post, from mg_latest_posts or mg_help_topics."New value: +"milli.gold news, mag or help post URL from mg_latest_posts or mg_help_topics."
  2. Addedv0.2.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavioral facts not in annotations: content is Persian, tables are flattened into pipe-delimited lines, and scope is limited to three post types. It stops short of saying what happens on an invalid or non-milli.gold URL.

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 the action and resource; the table-flattening detail and the URL constraint each carry distinct information with no filler.

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 two-parameter read tool with no output schema, the description covers the return shape (flattened text), content language, and accepted URL domain. The only missing piece is failure behavior for out-of-scope URLs, which is largely implied by the 'only milli.gold' constraint.

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%, with the url parameter documenting both its source tools and the accepted post types, and max_chars documenting the truncation range. The description adds nothing parameter-specific beyond output shape, so the baseline 3 applies.

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?

States a specific verb and resource ('Read the text of one Milli.gold news, magazine or help post') and adds a distinctive output trait (tables flattened to 'a | b | c' lines). This clearly separates it from the listing siblings mg_latest_posts and mg_help_topics, which only surface URLs.

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?

The line 'only milli.gold news, mag and help URLs' sets an explicit boundary on what may be passed in, which functions as a when-not rule. It does not name the sibling tools that produce valid URLs, though the schema's url description does that work.

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