Skip to content

MCP tools

Every tool is read-only (readOnlyHint: true, destructiveHint: false, idempotentHint: true) and returns JSON as one text block, the same JSON as the REST endpoint it names. tools/list shows only the tools the key’s scopes reach. A result is at most 40,000 characters: a list that would run longer is cut from the end and says so in a truncated field, with the cursor to carry on where the list pages.

Tool Title Scope Runs
get_workspace Workspace any key GET /workspace
list_signals Articles in scope signals:read GET /signals
list_outlooks Sector outlooks intel:read GET /outlooks
list_stories Stories intel:read GET /stories
get_story One story intel:read GET /stories/{id}
list_forecasts Forecasts intel:read GET /forecasts
list_coordination Coordination findings intel:read GET /coordination
list_reports Reports reports:read GET /reports
get_report One report reports:read GET /reports/{id}
list_sources Your sources sources:read GET /sources
list_source_items What your sources carried sources:read GET /sources/items

Workspace · any key · runs GET /workspace

The workspace this key belongs to: its name, the sectors and states it follows, coverage, report and alert settings, and the key’s scopes. Assistants call it first to learn what the other tools can return.

No arguments.

tools/call
{
"jsonrpc": "2.0",
"id": 7,
"method": "tools/call",
"params": {
"name": "get_workspace",
"arguments": {}
}
}

Try asking: “What does this workspace follow?”

The result’s text is the JSON documented on Get the workspace.

Articles in scope · scope signals:read · runs GET /signals

Articles in the workspace’s scope, newest first. Pages with next_cursor.

Argument Type Default Values What it does
sector string a sector key One sector key. Results stay inside the workspace’s own sectors.
state string a state slug One state or union territory slug.
q string up to 120 characters Words to find in the headline.
language string up to 8 characters ISO 639-1 language code, e.g. en, hi, ta.
since string (time) Only articles published after this time, as ISO 8601.
limit integer 25 1 to 200 How many articles to return. The REST default is 50.
cursor string next_cursor from a previous page.
tools/call
{
"jsonrpc": "2.0",
"id": 7,
"method": "tools/call",
"params": {
"name": "list_signals",
"arguments": {
"state": "ladakh",
"limit": 5
}
}
}

Try asking: “Show me the latest five articles about Ladakh.”

The result’s text is the JSON documented on List articles.

Sector outlooks · scope intel:read · runs GET /outlooks

The latest reading for each followed sector: risk score and level, direction, verdict and the stories driving it.

No arguments.

tools/call
{
"jsonrpc": "2.0",
"id": 7,
"method": "tools/call",
"params": {
"name": "list_outlooks",
"arguments": {}
}
}

Try asking: “Which of my sectors is rising this week, and why?”

The result’s text is the JSON documented on List sector outlooks.

Stories · scope intel:read · runs GET /stories

Stories in scope, with independent outlets, risk, place and a one-line reading.

Argument Type Default Values What it does
sector string a sector key One sector key. Results stay inside the workspace’s own sectors.
state string a state slug One state or union territory slug.
hours integer 72 1 to 720 How far back to look, in hours.
order string voices voices, risk, recent voices: most independent outlets first; risk: highest risk first; recent: newest first.
limit integer 20 1 to 100 How many stories to return.
tools/call
{
"jsonrpc": "2.0",
"id": 7,
"method": "tools/call",
"params": {
"name": "list_stories",
"arguments": {
"state": "manipur",
"order": "risk",
"limit": 5
}
}
}

Try asking: “What are the five riskiest stories in Manipur right now?”

The result’s text is the JSON documented on List stories.

One story · scope intel:read · runs GET /stories/{id}

One story in full: its reading, summary, places, articles, coverage by country and forecasts. A story outside the workspace’s scope answers not found.

Argument Type Default Values What it does
id required integer 1 to … The story id, from list_stories, list_signals or an outlook driver.
tools/call
{
"jsonrpc": "2.0",
"id": 7,
"method": "tools/call",
"params": {
"name": "get_story",
"arguments": {
"id": 297641
}
}
}

Try asking: “Tell me more about story 297641: who reported it and how do outlets differ?”

The result’s text is the JSON documented on Get a story.

Forecasts · scope intel:read · runs GET /forecasts

Forecasts in the workspace’s sectors, with counts and the track record.

Argument Type Default Values What it does
sector string a sector key One sector key. Results stay inside the workspace’s own sectors.
status string all open, awaiting, resolved, all open (unjudged, deadline ahead), awaiting (deadline passed, no verdict yet), resolved, or all.
limit integer 25 1 to 200 How many forecasts to return. The REST default is 100.
tools/call
{
"jsonrpc": "2.0",
"id": 7,
"method": "tools/call",
"params": {
"name": "list_forecasts",
"arguments": {
"status": "open",
"limit": 10
}
}
}

Try asking: “Which open forecasts fall due this week?”

The result’s text is the JSON documented on List forecasts.

Coordination findings · scope intel:read · runs GET /coordination

Coordination findings touching the workspace’s scope, each with its parties, mediums and evidence grade.

Argument Type Default Values What it does
grade string A, B, C Only findings of this evidence grade.
limit integer 10 1 to 60 How many findings to read before the grade filter. The REST default is 30.
tools/call
{
"jsonrpc": "2.0",
"id": 7,
"method": "tools/call",
"params": {
"name": "list_coordination",
"arguments": {
"limit": 5
}
}
}

Try asking: “Is anything in my scope looking organised? Who is behind it?”

The result’s text is the JSON documented on List coordination findings.

Reports · scope reports:read · runs GET /reports

The workspace’s compiled reports, newest first.

Argument Type Default Values What it does
limit integer 20 1 to 100 How many reports to return.
before string (time) Only reports made before this time, as ISO 8601.
tools/call
{
"jsonrpc": "2.0",
"id": 7,
"method": "tools/call",
"params": {
"name": "list_reports",
"arguments": {
"limit": 3
}
}
}

Try asking: “List my last three reports.”

The result’s text is the JSON documented on List reports.

One report · scope reports:read · runs GET /reports/{id}

One report. Markdown by default here (the REST default is JSON), in pages of at most 40,000 characters; each page ends with “Page n of m”.

Argument Type Default Values What it does
id required string (uuid) The report id, from list_reports.
format string markdown markdown, json markdown: the report as written; json: its structured content.
page integer 1 1 to … Which page of a long Markdown report to read.
tools/call
{
"jsonrpc": "2.0",
"id": 7,
"method": "tools/call",
"params": {
"name": "get_report",
"arguments": {
"id": "d35a4dc6-3109-41cf-a2a9-b9a7850ca1d1",
"page": 1
}
}
}

Try asking: “Summarise my latest weekly report in five bullets.”

The result’s text is the JSON documented on Get a report when format is json, or the report’s Markdown, one page at a time, when it is markdown.

Your sources · scope sources:read · runs GET /sources

The feeds the workspace follows, with each feed’s health.

No arguments.

tools/call
{
"jsonrpc": "2.0",
"id": 7,
"method": "tools/call",
"params": {
"name": "list_sources",
"arguments": {}
}
}

Try asking: “Are any of my feeds failing?”

The result’s text is the JSON documented on List sources.

What your sources carried · scope sources:read · runs GET /sources/items

What the workspace’s own feeds carried, newest first.

Argument Type Default Values What it does
source string (uuid) One source id, from list_sources.
sector string a sector key One sector key. Results stay inside the workspace’s own sectors.
state string a state slug One state or union territory slug.
since string (time) Only items published after this time, as ISO 8601.
q string up to 120 characters Words to find in the title.
limit integer 25 1 to 200 How many items to return. The REST default is 50.
tools/call
{
"jsonrpc": "2.0",
"id": 7,
"method": "tools/call",
"params": {
"name": "list_source_items",
"arguments": {
"limit": 5
}
}
}

Try asking: “What did my RBI feed publish today?”

The result’s text is the JSON documented on List source items.

The server’s own description of get_story, as a client sees it:

tools/list → get_story
{
"name": "get_story",
"title": "One story",
"description": "One story by id: its tag (sectors, event type, risk and its basis, named parties), summary, places, articles, coverage by country and forecasts. A story outside the workspace's scope answers not found. Same as GET /api/v1/stories/{id}.",
"inputSchema": {
"type": "object",
"properties": {
"id": {
"type": "integer",
"minimum": 1,
"description": "The story id, from list_stories, list_signals or an outlook driver."
}
},
"required": [
"id"
],
"additionalProperties": false
},
"annotations": {
"title": "One story",
"readOnlyHint": true,
"destructiveHint": false,
"idempotentHint": true,
"openWorldHint": false
}
}