Skip to main content
Glama

Coin links

get_coin_links
Read-only

Return the canonical MONETEKA website page and the Telegram Mini App link of one coin.

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": {
      "coin_id": "<coin_id>"
    },
    "name": "get_coin_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
coin_idYescoin_id from search_coins.

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofYes
warningsYes
request_idYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds only that the result is 'canonical' and includes a Telegram Mini App link, without saying what happens if no Mini App link exists or whether values can be null.

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?

A single front-loaded sentence with no filler; the return payload is stated before any qualifier, and nothing could be trimmed without losing content.

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?

A one-parameter read tool with full schema coverage, annotations, and an output schema carries most of its own documentation, so the description is nearly complete. The only gap is edge-case behavior for coins lacking a Mini App link.

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 itself states 'coin_id from search_coins', which is where the cross-tool reference lives. The description adds no further meaning about the identifier beyond what the schema provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (Return) and a precisely scoped resource: the canonical MONETEKA website page and the Telegram Mini App link for one coin. That is clearly distinguishable from siblings like get_coin_details or get_coin_prices, though it never names an alternative to sharpen the contrast.

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 by the noun 'links'; the description gives no explicit when-to-use condition, no exclusions, and no pointer to a sibling for related needs (e.g. details or prices). Adequate but leaves routing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources