Skip to main content
Glama

Get StrictScore daily pick

get_daily_pick
Read-onlyIdempotent

Returns the StrictScore daily pick (the asset selected for a date among those at or above the STRICT floor of 60) with its selection reasons, price at selection, latest price and performance since the pick. Use it when asked for the daily pick. Without a date it returns the latest pick, only if published within 36 hours. It is a research selection, not advice. Example arguments: {"date": "2026-11-05"}.

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

Input Schema

NameRequiredDescriptionDefault
dateNoPick date as YYYY-MM-DD. Omit for the latest pick.

Output Schema

NameRequiredDescriptionDefault
nameYes
slugYes
as_ofYesDate (YYYY-MM-DD) the result was served.
caveatYesOne-line methodology caveat: research, not investment advice; scenarios are not forecasts.
sectorNo
symbolYes
pickDateYesDate (YYYY-MM-DD) of the pick.
riskScoreYesRisk score, or null.
source_urlYesCanonical strictscore.com page to cite.
strictScoreYesSTRICT score, or null where the key account's report does not show it.
currentPriceYesLatest stored USD price, as a decimal string, or null.
priceAtSelectionYesUSD price when picked, as a decimal string, or null.
selectionReasonsYes
performanceSincePickYesPercent change since the pick, as a decimal string, or null.

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 genuinely new behavioral facts: the 36-hour publication window that governs whether the dateless call returns anything, the selection floor of 60, and the 'not advice' framing. It does not describe failure behavior when nothing qualifies beyond the window clause.

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?

The return payload is front-loaded in the first sentence, followed by the usage trigger and the default-behavior caveat, so the agent gets the essentials first. The trailing example argument is somewhat redundant given the schema's pattern and description for the sole parameter, costing a small amount of waste.

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?

An output schema exists, so return shape need not be explained, and the description covers purpose, trigger, default semantics, freshness constraint and disclaimer. For a single-optional-parameter read tool this is everything an agent needs before calling.

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% and the single parameter already documents the YYYY-MM-DD format and the omit-for-latest rule, so the baseline is 3. The description earns an extra point by attaching a constraint to the omitted case (results only if published within 36 hours) that the schema does not state.

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 ('Returns the StrictScore daily pick') and enumerates exactly what comes back: selection reasons, price at selection, latest price, performance since the pick. It also defines the qualifying criterion (assets at or above the STRICT floor of 60), which is what makes this tool distinguishable from the coin-analysis and rankings siblings.

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?

'Use it when asked for the daily pick' gives an explicit trigger, and the description states the default path when no date is supplied. It does not name an alternative tool or state when not to use it, which keeps it short of a 5.

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