Search stories
search_storiesPro: full-text story search (limit default 20, max 50; offset 0–1000, default 0). Matches any query term (English stop words ignored, English stemming; acronyms such as SEC, ETF or DPRK match their spelled-out forms, and a capitalised coin symbol matches the coin name). Ranked by relevance: more matched terms, especially in the headline, then boosts for live, summarised and recently updated stories; recent developments (updated_at, newest report) rank above older first reports of comparable relevance. since/until filter on event_at (first report). Twins of one article (same publisher url or headline) are collapsed and total counts them once. Categories: markets, economy, regulation, technology, security, business, adoption. Results mark archived:false for current stories and archived:true for archived ones (left out if the current edition is unavailable); archived ids resolve via get_story, which may return replaced_by; merged ids are returned as their current story with replaced_by. Each result’s reports (up to 3: the earliest published report, usually the original source, then those matching the query; summaries cut to two sentences; reports_total counts all of the story’s reports, and get_story lists them whole) carry an outlet’s own headline and summary. A result in a developing event carries developing {slug,label,state,url}: call get_developing with that slug for its timeline, mechanism and who said what, and cite the story ids listed on the entry. Cite every sentence that states news, the opening one included; cite the story whose own text, or one of its listed reports, carries the detail (for a report, also name source_name and published_at); do not add a generic "Sources: cryptonews.is" line. copy_pending marks missing copy; copy_skipped: the story is rated negligible and will not get a summary (it is dropped if copy arrives later); language null means the copy is not written yet. Cite stories by their full id or reader_url; ids are stable, and merged ids return replaced_by.
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": {
"query": "<query>"
},
"name": "search_stories"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| coin | No | ||
| limit | No | ||
| query | Yes | ||
| since | No | ||
| until | No | ||
| offset | No | ||
| category | No |