Skip to main content
Glama

Get full StrictScore analysis

get_coin_analysis
Read-onlyIdempotent

Returns the full StrictScore analysis of one asset: STRICT score and six pillar ratings, risk score and factors, upside and probability, hype narratives, overview, thesis, strengths, risks, catalysts, price scenarios, last analyzed date and the page URL. Use it after search_coins when the user wants depth on one asset. Not for several assets side by side (use compare_coins) or a quick lookup (search_coins is lighter). Example arguments: {"slug": "ethereum", "locale": "en"}.

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": {
      "slug": "<slug>"
    },
    "name": "get_coin_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesStrictScore slug as returned by search_coins, for example "bitcoin" or "ethereum".
localeNoLanguage of the written analysis (overview, thesis, risks). Scores and numbers do not change.en

Output Schema

NameRequiredDescriptionDefault
nameYesAsset name.
rankYesMarket-cap rank, or null.
slugYesIdentifier to pass to get_coin_analysis and compare_coins.
as_ofYesDate (YYYY-MM-DD) the result was served.
priceYesLive USD price, or null when unavailable.
risksYes
caveatYesOne-line methodology caveat: research, not investment advice; scenarios are not forecasts.
sectorYesStrictScore sector, or null.
symbolYesTicker symbol.
pillarsYesPillar ratings (sustainability, transparency, revenue, innovation, community, tokenomics); null where not applicable.
overviewYes
catalystsYes
marketCapYesMarket capitalisation in USD, or null.
maxUpsideYesUpside estimate of the analysis, or null.
riskScoreYesRisk score, or null.
strengthsYes
volume24hYes24h volume in USD, or null.
conclusionYes
source_urlYesCanonical strictscore.com page to cite.
probabilityYesProvisional 12-month probability estimate, or null.
riskFactorsYes
strictScoreYesSTRICT score 0-100, or null when no StrictScore analysis exists.
lastAnalyzedYesDate the analysis was last updated.
priceTargetsYesBear, base and bull scenarios; not forecasts.
cyclePotentialYesCycle upside multiple of the analysis (same value as maxUpside), or null.
hypeNarrativesYes
priceChange24hYes24h price change in percent, or null.
recommendationYesEngine signal label, a model output; not investment advice. Null where none is published.
cycleProbabilityYesProvisional probability estimate (same value as probability), or null.
investmentThesisYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 closed-world, so the safety profile is covered. The description adds real value by disclosing the workflow prerequisite (slug must come from search_coins) and that this is the heavyweight 'full' endpoint. It does not mention payload size, latency, or what happens for an unknown slug — minor gaps given the annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the outcome, then usage routing, then exclusions, then an example — a sensible order. The long enumeration of returned fields is the only excess, since an output schema already exists, but it reads as a single efficient list rather than padding.

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?

With an output schema present the description needn't explain return values, and annotations plus a 100%-documented 2-parameter schema cover the rest. The description still supplies the workflow context (search first) and sibling routing, so an agent has everything needed to call it correctly.

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% — both slug and locale are fully documented in the schema, including the enum and the note that locale affects only prose, not scores. The description's example arguments and its 'slug as returned by search_coins' hint restate what the schema already says, so 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?

Opens with a specific verb and resource ("Returns the full StrictScore analysis of one asset") and enumerates the payload (STRICT score, six pillars, risk factors, scenarios, thesis). It is clearly distinguishable from compare_coins and search_coins by scope: one asset, full depth.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the trigger ("after search_coins when the user wants depth on one asset") and two exclusions with named alternatives: not several assets (compare_coins) and not a quick lookup (search_coins is lighter). Nothing is left to inference about when to pick this tool.

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