proofite

Read your AI-written daily briefing and retune the filter behind it: feeds, newsletters, topics.

사용해야 할까요

품질 및 안전성

A
설명 품질
97%
스키마 완전성
85%
이름 품질
95%
오염 위험
100%
권한 일치
90%
프로토콜 준수
100%

발견 사항 (1)

  • LOWTool 'remove_web_search' suggests web access but openWorldHint=falseremove_web_search에서

도구 정의와 프로토콜 준수에 대한 자동 분석을 기반으로 합니다.

컨텍스트 비용

~10,048토큰 (도구 정의)
~1.0 KB일반적인 응답 크기
상당한 주의 영향 (128k 컨텍스트의 7.85%)

이는 서버의 도구가 모델의 컨텍스트에 로드될 때마다 소비되는 대략적인 토큰 수입니다. 수치가 높을수록 다른 작업에 사용할 수 있는 주의가 줄어듭니다.

설치

원클릭 설치

`claude_desktop_config.json` 파일에 다음을 추가하세요:

{
  "mcpServers": {
    "proofite": {
      "command": "npx",
      "args": [
        "proofite-mcp"
      ]
    }
  }
}

실행 가능한 패키지

npmproofite-mcp1.2.0stdio

원격 엔드포인트

https://proofite.com/mcpstreamable-http

할 수 있는 일

도구 목록

도구 (47)

🟢 읽기 전용🟡 쓰기🔴 삭제⚪ 알 수 없음
🟢get_briefing(briefing_id, include_markdown)

Read the user's personal AI-written news briefing (daily digest) in full markdown: every story selected today from their newsletters, RSS feeds and monitored web searches, with sources. Returns the latest briefing by default, or a specific one by id or date. Also returns an index of entry ids, needed to rate or correct individual stories.

입력 스키마

{
  "type": "object",
  "properties": {
    "briefing_id": {
      "type": "string",
      "description": "Specific briefing id (from list_briefings). Omit for the latest."
    },
    "include_markdown": {
      "type": "boolean",
      "description": "Include the full text. Default true; set false for just the index."
    }
  },
  "additionalProperties": false
}
🟢list_briefings(limit, offset)

List the user's past daily briefings (most recent first) with date, title, number of stories and whether an episode exists. Use it to find the id of a specific day before reading or correcting it.

입력 스키마

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50,
      "description": "How many, default 10"
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Skip the N most recent: use it to walk back through an archive longer than 50 (default 0)"
    }
  },
  "additionalProperties": false
}
🟢search_briefings(query, limit)

Search the person's past daily briefings for a word or a phrase, in the titles and in the text of every story, newest first. Each result has the briefing id, date and title, the passage around the match and, when the match is inside a story, that story's entry id and headline, with the link that opens the briefing right there. Use it for "when did you tell me about X?" or "find that piece on Y", then read the briefing with get_briefing. The match is literal, with no synonyms: if nothing comes back, try a shorter word or another spelling. The reading list has its own search (list_saved).

입력 스키마

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "The word or phrase to look for, at least two characters"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 30,
      "description": "How many briefings at most (default 10)"
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}
🟢get_information_diet

Read everything that shapes what reaches this person: delivery schedule, length, technicality, depth, stance, tone and entry mix, podcast format (two-host show or single voice), voice accent and whether the podcast is auto-paused, stated interests and no-go topics, the profile the system has learned about them, the per-topic preferences built from their feedback (affinity, muted, followed themes) and the specific stories they pinned with "follow" (every development of those gets reported). This is the full picture of their news filter — read it before changing anything.

입력 스키마

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢list_sources

List the topic inboxes this person feeds their briefing with: each one has a dedicated email address for newsletter subscriptions, plus RSS feeds and monitored web searches. Shows how much each produced recently, its priority and whether it is included in the briefing.

입력 스키마

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢get_source(source_id)

Inspect one topic inbox in detail: every RSS feed (with its health and last fetch), every monitored web search, X/Twitter profiles, and the newsletters currently arriving at its dedicated address. Use it before removing or reorganising anything.

입력 스키마

{
  "type": "object",
  "properties": {
    "source_id": {
      "type": "string",
      "description": "Id from list_sources"
    }
  },
  "required": [
    "source_id"
  ],
  "additionalProperties": false
}
🟢get_podcast_episode(briefing_id)

Get the audio episode generated from a briefing: a private podcast in the user's language — by default a show with two hosts who talk the news through, or a single voice in the classic format — with a playable URL, the private RSS feed URL and the show notes listing every source. Returns the latest episode by default. For the words themselves use get_episode_transcript.

입력 스키마

{
  "type": "object",
  "properties": {
    "briefing_id": {
      "type": "string",
      "description": "Episode of a specific briefing. Omit for the latest."
    }
  },
  "additionalProperties": false
}
🟢get_episode_transcript(briefing_id, episode_id)

The full text of a podcast episode, word for word: the script the voices read. In the two-host show it comes as "Name: line" turns; in the classic format as plain paragraphs. Use it when the person wants a passage quoted, a point the hosts made that the written briefing does not have, or to search what was said. Latest episode by default.

입력 스키마

{
  "type": "object",
  "properties": {
    "briefing_id": {
      "type": "string",
      "description": "The episode of a specific briefing. Omit for the latest."
    },
    "episode_id": {
      "type": "string",
      "description": "A specific episode (from get_podcast_episode). Wins over briefing_id."
    }
  },
  "additionalProperties": false
}
🟢list_read_later

List what is queued in the read-later inbox: links and forwarded emails that are guaranteed to be covered in the next briefing, and — apart — the stories the person deferred to a later day ("snoozed"), which wait until their date.

입력 스키마

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢list_deep_dives

List the deep-dive research requests waiting to be covered: topics the user asked the briefing to investigate with fresh web research.

입력 스키마

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢list_inserts

The inserts: optional extra pages of the daily briefing that the person switches on one by one — weather for their city, their fantasy-football roster (Italian users), the stocks they hold, a daily rebus puzzle. Returns, in the person's language, each insert with what it does, whether it is on, its current configuration, the fields it needs (with types) and the AI levels it offers. Read this before configure_insert.

입력 스키마

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢get_insert(insert)

Everything about ONE insert (an optional extra page of the briefing; the list is in list_inserts), in the person's language: what it does and how it works, how often it shows up and where it sits in the briefing, its short guide, its data sources, the AI levels it offers, every configuration field with its options and its current value, and this person's state: on or off, configured or not, the level, the configuration summed up in a phrase, the link that opens it in the app. Use it to explain an insert or to prepare configure_insert.

입력 스키마

{
  "type": "object",
  "properties": {
    "insert": {
      "type": "string",
      "enum": [
        "meteo",
        "aria",
        "allerte",
        "valanghe",
        "cielo",
        "lanci",
        "terremoti",
        "emergenze",
        "primapagina",
        "agenda",
        "tendenze",
        "parole",
        "verifica",
        "addio",
        "cdm",
        "parlamento",
        "fuorisacco",
        "resume",
        "portaccanto",
        "rassegna",
        "borsa",
        "cambi",
        "cripto",
        "prezzo",
        "casa",
        "luce",
        "carburanti",
        "scadenze",
        "statoete",
        "richiami",
        "squadra",
        "campionato",
        "fantacalcio",
        "formula1",
        "motogp",
        "tennis",
        "basket",
        "pallavolo",
        "rugby",
        "nfl",
        "hockey",
        "golf",
        "sapere",
        "foto",
        "opera",
        "lingua",
        "corso",
        "serie",
        "musica",
        "podcast",
        "video",
        "rebus",
        "quiz",
        "parola",
        "cruciverba",
        "sudoku",
        "scacchi",
        "anno",
        "cronologia",
        "luogo",
        "almanacco",
        "feste",
        "viaggio",
        "volo",
        "citta",
        "eventi",
        "scioperi",
        "chicca",
        "smalltalking",
        "riepilogo"
      ],
      "description": "The insert id (from list_inserts)"
    }
  },
  "required": [
    "insert"
  ],
  "additionalProperties": false
}
🟡configure_insert(insert, enabled, level, config)

Configure one insert of the briefing. Call list_inserts first: it returns, for each insert available to this person (language and country already applied), the config fields with their key, type and options. Pass the insert id and any subset of: enabled (true/false), level (one of the insert's AI levels: nessuno = data only, leggero = the podcast hosts mention it, medio = plus a short written comment), config (an object keyed by the field keys). Field types: "luoghi" takes city names as strings (e.g. {"citta": ["Verona"]}; resolved to coordinates here), "lista_testo" takes an array of strings or the pasted text under "<key>_testo", "titoli"/"squadra" take names as strings, "scelta" takes one option id, "scelta_multipla" an array of option ids, "testo" a string. Examples: meteo {"citta": ["Verona", "Milano"], "orizzonte": "weekend"}; fantacalcio {"rosa": ["Contini", "Milinkovic-Savic V."], "lega": "…"}; borsa {"titoli": ["Enel", "Nvidia"]}; rebus {"livello_gioco": "facile", "quando": "weekend"}. Switching on requires a valid configuration. Takes effect from the next briefing.

입력 스키마

{
  "type": "object",
  "properties": {
    "insert": {
      "type": "string",
      "enum": [
        "meteo",
        "aria",
        "allerte",
        "valanghe",
        "cielo",
        "lanci",
        "terremoti",
        "emergenze",
        "primapagina",
        "agenda",
        "tendenze",
        "parole",
        "verifica",
        "addio",
        "cdm",
        "parlamento",
        "fuorisacco",
        "resume",
        "portaccanto",
        "rassegna",
        "borsa",
        "cambi",
        "cripto",
        "prezzo",
        "casa",
        "luce",
        "carburanti",
        "scadenze",
        "statoete",
        "richiami",
        "squadra",
        "campionato",
        "fantacalcio",
        "formula1",
        "motogp",
        "tennis",
        "basket",
        "pallavolo",
        "rugby",
        "nfl",
        "hockey",
        "golf",
        "sapere",
        "foto",
        "opera",
        "lingua",
        "corso",
        "serie",
        "musica",
        "podcast",
        "video",
        "rebus",
        "quiz",
        "parola",
        "cruciverba",
        "sudoku",
        "scacchi",
        "anno",
        "cronologia",
        "luogo",
        "almanacco",
        "feste",
        "viaggio",
        "volo",
        "citta",
        "eventi",
        "scioperi",
        "chicca",
        "smalltalking",
        "riepilogo"
      ],
      "description": "The insert id"
    },
    "enabled": {
      "type": "boolean",
      "description": "Switch it on (true) or off (false)"
    },
    "level": {
      "type": "string",
      "enum": [
        "nessuno",
        "leggero",
        "medio"
      ],
      "description": "How much the AI talks about it, where the insert offers levels"
    },
    "config": {
      "type": "object",
      "description": "The insert's configuration (see the description)",
      "additionalProperties": true
    }
  },
  "required": [
    "insert"
  ],
  "additionalProperties": false
}
🟡rate_insert(insert, stars, comment)

Leave feedback on one insert of the briefing for the people who build it: stars from 1 to 5 and/or a comment of up to 1000 characters, at least one of the two. Use it when the person judges an insert — "the weather page is great", "the quiz is too hard", "the stocks insert is missing my bank" — passing the insert id (see list_inserts), the stars if they gave a grade, and the comment in their own words. A second call within fifteen minutes completes or corrects the same feedback instead of adding another; later calls add a new one. Comments reach the founder; stars are read in aggregate. Returns the current average for that insert.

입력 스키마

{
  "type": "object",
  "properties": {
    "insert": {
      "type": "string",
      "enum": [
        "meteo",
        "aria",
        "allerte",
        "valanghe",
        "cielo",
        "lanci",
        "terremoti",
        "emergenze",
        "primapagina",
        "agenda",
        "tendenze",
        "parole",
        "verifica",
        "addio",
        "cdm",
        "parlamento",
        "fuorisacco",
        "resume",
        "portaccanto",
        "rassegna",
        "borsa",
        "cambi",
        "cripto",
        "prezzo",
        "casa",
        "luce",
        "carburanti",
        "scadenze",
        "statoete",
        "richiami",
        "squadra",
        "campionato",
        "fantacalcio",
        "formula1",
        "motogp",
        "tennis",
        "basket",
        "pallavolo",
        "rugby",
        "nfl",
        "hockey",
        "golf",
        "sapere",
        "foto",
        "opera",
        "lingua",
        "corso",
        "serie",
        "musica",
        "podcast",
        "video",
        "rebus",
        "quiz",
        "parola",
        "cruciverba",
        "sudoku",
        "scacchi",
        "anno",
        "cronologia",
        "luogo",
        "almanacco",
        "feste",
        "viaggio",
        "volo",
        "citta",
        "eventi",
        "scioperi",
        "chicca",
        "smalltalking",
        "riepilogo"
      ],
      "description": "The insert id"
    },
    "stars": {
      "type": "integer",
      "minimum": 1,
      "maximum": 5,
      "description": "The grade, 1 (poor) to 5 (excellent)"
    },
    "comment": {
      "type": "string",
      "maxLength": 1000,
      "description": "What they like, what is missing, in their words"
    }
  },
  "required": [
    "insert"
  ],
  "additionalProperties": false
}
🟢list_saved(query, limit)

The reading list: stories the person saved from their briefings (including the "chicca", the archive story of quiet days), newest first, each with the briefing it came from. Pass `query` to search them by any word — title, text, topics, briefing title. To add or remove: save_entry, unsave_entry.

입력 스키마

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Optional: a word to search for"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "description": "How many to return (default 30)"
    }
  },
  "additionalProperties": false
}
🟢get_account

Account status: plan, whether the briefing is currently running, when the next one is due, how many sources and stories are in the system, and the AI cost accrued this month.

입력 스키마

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢list_features(family)

What Proofite can do for this person, feature by feature and grouped by family (reading, listening, correcting, sharing…): for each feature a short explanation, its state for THIS account (on; off, with the setting that switches it on; or "not yet", with what has to happen first), a personal example from their own numbers when there is one, and the page of the app where it lives. Use it to answer "what can I do with Proofite?", "is X on?" or "why don't I see X?" before changing anything. The texts are in Italian, the language the app is written in: say them in the person's language. Settings change with update_information_diet, inserts with configure_insert.

입력 스키마

{
  "type": "object",
  "properties": {
    "family": {
      "type": "string",
      "description": "Optional: only one family, by id (leggere = reading, ascoltare = listening, correggere = correcting, condividere = sharing; the full answer lists them all)"
    }
  },
  "additionalProperties": false
}
🟢get_page_help(path)

Given a page of the Proofite app (the path from the address bar, like /app/digests, /app/edicola, /app/settings, or a full link), says what that page is, what can be done there and which features live on it, with their state for this person; on a briefing or an inbox it also says which one. Use it when the person asks "what is this?", "what can I do here?" or "where do I find X?" about the screen in front of them. The texts are in Italian, the language the app is written in: say them in the person's language. An unknown path gets the list of the pages that exist.

입력 스키마

{
  "type": "object",
  "properties": {
    "path": {
      "type": "string",
      "description": "The page: a path of the app (/app/settings, /settings) or a full link (https://proofite.com/app/digests/…)"
    }
  },
  "required": [
    "path"
  ],
  "additionalProperties": false
}
🟡update_information_diet(digest_enabled, digest_time, digest_days, digest_length, technicality, ...)

Change how and when the briefing reaches this person: delivery time and days, length, technicality, depth, stance, tone, entry mix (few deep stories vs many short ones), stated interests and topics to avoid, language, timezone; the podcast (on/off, minutes, two-host show or single voice, voice accent), email delivery, the weekly recap, the chicca on quiet days, the smalltalking stories, web enrichment. Pass only the keys you want to change. Read get_information_diet first — these are global settings, not per-topic ones (for a single topic use tune_topic).

입력 스키마

{
  "type": "object",
  "properties": {
    "digest_enabled": {
      "description": "ricevere o meno il briefing quotidiano",
      "type": "boolean"
    },
    "digest_time": {
      "description": "orario di consegna, HH:MM nel fuso dell'utente",
      "type": "string"
    },
    "digest_days": {
      "description": "giorni della settimana, ISO 1=lunedì … 7=domenica",
      "type": "array",
      "items": {
        "type": "integer",
        "minimum": 1,
        "maximum": 7
      }
    },
    "digest_length": {
      "description": "quanto deve essere lungo",
      "type": "string",
      "enum": [
        "short",
        "medium",
        "long",
        "xlong",
        "full"
      ]
    },
    "technicality": {
      "description": "1 divulgativo … 5 da addetti ai lavori",
      "type": "integer",
      "minimum": 1,
      "maximum": 5
    },
    "depth": {
      "description": "1 solo i fatti … 5 analisi e implicazioni",
      "type": "integer",
      "minimum": 1,
      "maximum": 5
    },
    "entry_mix": {
      "description": "1 poche voci trattate a fondo … 5 tante voci brevi (la lunghezza totale non cambia)",
      "type": "integer",
      "minimum": 1,
      "maximum": 5
    },
    "brevi_spiegate": {
      "description": "sotto ogni breve due o tre frasi di spiegazione (di cosa si tratta, perché conta); spento = una sola frase di perché",
      "type": "boolean"
    },
    "stance": {
      "description": "1 neutro … 5 l'editor si sbilancia",
      "type": "integer",
      "minimum": 1,
      "maximum": 5
    },
    "tone": {
      "description": "come deve scrivere («diretto, zero fuffa»)",
      "type": "string"
    },
    "interests": {
      "description": "cosa seguire, in linguaggio naturale",
      "type": "string"
    },
    "avoid": {
      "description": "cosa non vuole leggere mai",
      "type": "string"
    },
    "language": {
      "description": "lingua del briefing e del podcast (codice ISO 639-1)",
      "type": "string",
      "enum": [
        "it",
        "en",
        "es",
        "de",
        "fr",
        "pt",
        "nl",
        "pl",
        "ro",
        "tr",
        "sv",
        "da",
        "nb",
        "fi",
        "cs",
        "hu",
        "el",
        "ru",
        "uk",
        "ja",
        "ko",
        "hi",
        "id",
        "vi",
        "th",
        "zh",
        "ar",
        "he",
        "bn",
        "ur",
        "zt"
      ]
    },
    "timezone": {
      "description": "fuso orario IANA (Europe/Rome)",
      "type": "string"
    },
    "podcast_enabled": {
      "description": "generare anche l'episodio audio",
      "type": "boolean"
    },
    "podcast_minutes": {
      "description": "durata desiderata dell'episodio",
      "type": "integer",
      "minimum": 2,
      "maximum": 20
    },
    "podcast_formato": {
      "description": "show = due conduttori che si rispondono (il formato di casa); classico = una voce che legge il briefing",
      "type": "string",
      "enum": [
        "show",
        "classico"
      ]
    },
    "podcast_accento": {
      "description": "accento della voce, per la lingua scelta: inglese us/gb/au/ie/in, spagnolo es/latam, francese fr/ca, tedesco de/at/ch (l'italiano non ha varianti); null = automatico, abbinato alla lingua",
      "type": [
        "string",
        "null"
      ],
      "enum": [
        "us",
        "gb",
        "au",
        "ie",
        "in",
        "es",
        "latam",
        "fr",
        "ca",
        "br",
        "pt",
        "de",
        "at",
        "ch",
        null
      ]
    },
    "email_digest_enabled": {
      "description": "ricevere il briefing anche per email",
      "type": "boolean"
    },
    "weekly_recap_enabled": {
      "description": "il riepilogo della settimana in fondo al briefing, il giorno scelto (è l'inserto «riepilogo» dell'Edicola)",
      "type": "boolean"
    },
    "chicca_enabled": {
      "description": "nei giorni senza notizie, una storia vera dall'archivio (è l'inserto «chicca» dell'Edicola)",
      "type": "boolean"
    },
    "smalltalking_enabled": {
      "description": "ogni giorno, in coda al briefing, due o tre storie brevi da raccontare (è l'inserto «smalltalking» dell'Edicola)",
      "type": "boolean"
    },
    "serper_enrich": {
      "description": "arricchire il briefing con ricerche web fresche",
      "type": "boolean"
    }
  },
  "description": "Any subset of the settings.",
  "additionalProperties": false
}
🟢tune_topic(topic, topics, action)

Tune how a single topic — or a COMBINATION of labels — is treated in future briefings: more or less of it, more or less technical, deeper or shorter, more or less often, muted entirely, or followed so every development of that WHOLE THEME gets reported (to follow one specific story, use rate_briefing_entry with "follow" on that entry). `topic` is one key: a free tag ("intelligenza artificiale") or a typed label (e:tesla, c:auto, f:soldi); `topics` instead is a list of labels combined with AND ("e:tesla"+"f:soldi" = Tesla only when about money — Tesla alone stays as it is). This is the precise instrument — for a vague comment like "too much crypto lately" use correct_briefing instead.

입력 스키마

{
  "type": "object",
  "properties": {
    "topic": {
      "type": "string",
      "description": "One key: a topic as it appears in get_information_diet or in a briefing entry (e.g. \"intelligenza artificiale\", \"e:tesla\", \"c:auto\")"
    },
    "topics": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 4,
      "description": "Alternative to topic: labels to COMBINE with AND (e.g. [\"e:tesla\",\"f:soldi\"])"
    },
    "action": {
      "type": "string",
      "enum": [
        "more",
        "less",
        "more_technical",
        "simpler",
        "deeper",
        "shorter",
        "more_often",
        "less_often",
        "mute",
        "unmute",
        "follow",
        "unfollow"
      ],
      "description": "What to change about it"
    }
  },
  "required": [
    "action"
  ],
  "additionalProperties": false
}
🟢correct_briefing(note, briefing_id, entry_id)

Tell the briefing what was wrong with it, in plain language — "too much crypto and not enough on the EU regulation", "keep it shorter", "explain the technical parts more simply". An AI editor reads the note against the actual briefing and turns it into concrete adjustments: topic preferences, settings (technicality, depth, length, podcast minutes, tone), deep-dive requests. This is the main way a person retunes their news feed by talking. To pin ONE story so its developments get reported, pass its entry_id with the note, or use rate_briefing_entry with "follow": a note without entry_id can only follow a whole theme.

입력 스키마

{
  "type": "object",
  "properties": {
    "note": {
      "type": "string",
      "description": "What was wrong or what they want changed, in their own words"
    },
    "briefing_id": {
      "type": "string",
      "description": "Which briefing the note refers to. Omit for the latest."
    },
    "entry_id": {
      "type": "string",
      "description": "Optional: the specific story the note is about (entry id from get_briefing)"
    }
  },
  "required": [
    "note"
  ],
  "additionalProperties": false
}
🟢rate_briefing_entry(entry_id, signal, topics, briefing_id, withdraw)

Give a precise up/down signal on one story of a briefing: more like this, less like this, more technical, simpler, deeper, shorter, or mute. A story carries typed labels (see `labels` in get_briefing): e:<who or what> (e:tesla), c:<field, its world> (c:auto), f:<angle> (f:soldi = money) and free tags. `topics` chooses the LEVEL: one label = broad ("less of Tesla, everywhere"); several labels = narrow, they are COMBINED with AND ("less of Tesla + soldi" = Tesla only when the story is about money; Tesla alone and money stories of others are untouched). Omit `topics` for the whole story (all its labels together, the narrowest level). Sending the same signal again with different topics REPLACES the previous one. "follow" is different: it pins THIS story — every development of it (and only of it) gets a full entry; "unfollow" releases it. `withdraw: true` takes a signal back.

입력 스키마

{
  "type": "object",
  "properties": {
    "entry_id": {
      "type": "string",
      "description": "Entry id from get_briefing"
    },
    "signal": {
      "type": "string",
      "enum": [
        "more",
        "less",
        "more_technical",
        "simpler",
        "deeper",
        "shorter",
        "more_often",
        "less_often",
        "mute",
        "follow",
        "unfollow"
      ],
      "description": "The signal to record"
    },
    "topics": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 6,
      "description": "Labels of this story to combine (AND), from `labels` in get_briefing — e.g. [\"e:tesla\"] for Tesla everywhere, [\"e:tesla\",\"f:soldi\"] for Tesla only about money. Omit for the whole story."
    },
    "briefing_id": {
      "type": "string",
      "description": "Which briefing. Omit for the latest."
    },
    "withdraw": {
      "type": "boolean",
      "description": "true = take back the signal of this kind previously given on this story (the topics it had touched are restored). With \"follow\" use \"unfollow\" instead."
    }
  },
  "required": [
    "entry_id",
    "signal"
  ],
  "additionalProperties": false
}
🟢unfollow_story(story_id)

Release a pinned story by its id (from get_information_diet → followed_stories), so its developments stop getting a dedicated entry. Works even when the briefing it came from is gone — rate_briefing_entry "unfollow" needs the briefing, this does not.

입력 스키마

{
  "type": "object",
  "properties": {
    "story_id": {
      "type": "string",
      "description": "The story id listed by get_information_diet"
    }
  },
  "required": [
    "story_id"
  ],
  "additionalProperties": false
}
🟢report_missing_story(text, briefing_id)

The reader expected a story and the briefing did not have it. Describe it in their words; the editor investigates their own sources of the last days, today's briefing, their preferences and a web search, and answers with a verdict: it was in the briefing, none of their sources carried it (and proposes the missing source), it was dropped because of a preference (and corrects it), it was seen but undervalued, or it could not be found. Topics get followed so similar stories do not slip again; a deep-dive may be queued for the next briefing. Five per day.

입력 스키마

{
  "type": "object",
  "properties": {
    "text": {
      "type": "string",
      "description": "What story they expected, in their own words"
    },
    "briefing_id": {
      "type": "string",
      "description": "Which briefing it was missing from. Omit for the latest."
    }
  },
  "required": [
    "text"
  ],
  "additionalProperties": false
}
🟢list_missing_reports(briefing_id)

The investigations opened with report_missing_story on a briefing: what was asked, the verdict, the explanation, the signals applied and — when none of the person's sources carried the story — the source proposed, with whether it was already added. Latest briefing by default.

입력 스키마

{
  "type": "object",
  "properties": {
    "briefing_id": {
      "type": "string",
      "description": "Which briefing. Omit for the latest."
    }
  },
  "additionalProperties": false
}
🟡add_proposed_source(report_id)

When report_missing_story found that none of the person's sources carried the story, it proposed one. This adds that proposed feed to the inbox it indicated — the same tap the reader has under the briefing. Idempotent: adding twice says it was already added.

입력 스키마

{
  "type": "object",
  "properties": {
    "report_id": {
      "type": "string",
      "description": "The investigation id, from list_missing_reports or the report_missing_story result"
    }
  },
  "required": [
    "report_id"
  ],
  "additionalProperties": false
}
🔴set_learned_profile(text, mode)

Read or rewrite the free-text profile the briefing uses to know who this person is — their work, projects, recurring interests, what they already know. Appending is usually better than replacing: pass mode "append" to add a line.

입력 스키마

{
  "type": "object",
  "properties": {
    "text": {
      "type": "string",
      "description": "The profile text, or the line to add"
    },
    "mode": {
      "type": "string",
      "enum": [
        "append",
        "replace"
      ],
      "description": "Default append"
    }
  },
  "required": [
    "text"
  ],
  "additionalProperties": false
}
⚪request_deep_dive(query)

Ask the next briefing to investigate a topic properly, with fresh web research: it will include a mini-dossier with sources. Use it whenever the person says "I want to know more about X" or "keep digging on this".

입력 스키마

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "The question or topic to research"
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}
🔴cancel_deep_dive(deep_dive_id)

Remove a deep-dive request that is still waiting (ids from list_deep_dives). One already covered in a briefing cannot be cancelled.

입력 스키마

{
  "type": "object",
  "properties": {
    "deep_dive_id": {
      "type": "string",
      "description": "The request id, from list_deep_dives"
    }
  },
  "required": [
    "deep_dive_id"
  ],
  "additionalProperties": false
}
🟡save_for_later(url, text, title)

Put a link or a note into the read-later queue: whatever lands there is guaranteed to be covered in the next briefing. The page is fetched and its text stored, so it can be summarised even if the site later blocks access.

입력 스키마

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The link to save"
    },
    "text": {
      "type": "string",
      "description": "Alternative to url: a free-text note to keep"
    },
    "title": {
      "type": "string",
      "description": "Optional title for a text note"
    }
  },
  "additionalProperties": false
}
🟡save_entry(entry_id, briefing_id)

Keep one story of a briefing in the reading list (list_saved): a snapshot that survives even if the briefing is deleted. entry_id "chicca" saves the chicca — the archive story of quiet days — when the briefing has one. Saving again only refreshes the date.

입력 스키마

{
  "type": "object",
  "properties": {
    "entry_id": {
      "type": "string",
      "description": "Entry id from get_briefing, or \"chicca\""
    },
    "briefing_id": {
      "type": "string",
      "description": "Which briefing. Omit for the latest."
    }
  },
  "required": [
    "entry_id"
  ],
  "additionalProperties": false
}
🔴unsave_entry(saved_id, entry_id, briefing_id)

Take a story out of the reading list, by its saved id (from list_saved) or by briefing + entry id.

입력 스키마

{
  "type": "object",
  "properties": {
    "saved_id": {
      "type": "string",
      "description": "The id from list_saved"
    },
    "entry_id": {
      "type": "string",
      "description": "Alternative: the entry id in its briefing"
    },
    "briefing_id": {
      "type": "string",
      "description": "With entry_id: which briefing. Omit for the latest."
    }
  },
  "additionalProperties": false
}
🟡share_briefing(briefing_id, podcast)

Create (or read) the public link of a briefing: a cleaned-up read-only copy — no personal "why this matters to you" notes, no name. The podcast episode comes along only if `podcast` is true: the hosts greet the reader by name, so that is the reader's call. Idempotent: calling again returns the same link; unshare_briefing revokes it.

입력 스키마

{
  "type": "object",
  "properties": {
    "briefing_id": {
      "type": "string",
      "description": "Which briefing. Omit for the latest."
    },
    "podcast": {
      "type": "boolean",
      "description": "Include the episode in the shared page (default: unchanged, initially false)"
    }
  },
  "additionalProperties": false
}
🔴unshare_briefing(briefing_id)

Revoke the public link of a briefing: the page and its audio stop answering immediately.

입력 스키마

{
  "type": "object",
  "properties": {
    "briefing_id": {
      "type": "string",
      "description": "Which briefing. Omit for the latest."
    }
  },
  "additionalProperties": false
}
🟢generate_podcast_episode(briefing_id)

Make (or remake) the podcast episode of a briefing right away — the latest by default. Takes a few minutes (script, then voices); poll with get_podcast_episode. Asking for an episode is a listening signal: it also lifts the automatic pause. Costs real AI money, so only when asked.

입력 스키마

{
  "type": "object",
  "properties": {
    "briefing_id": {
      "type": "string",
      "description": "Which briefing. Omit for the latest."
    }
  },
  "additionalProperties": false
}
🟢resume_podcast

The podcast pauses itself when nobody listens for a while (no episodes get made; the setting podcast_enabled stays true). This lifts the pause: from tomorrow the episode comes back every morning. get_information_diet and get_account say whether it is paused.

입력 스키마

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢generate_briefing

Generate a briefing immediately instead of waiting for the scheduled time, using everything collected so far. Costs real AI money and takes a couple of minutes, so use it only when explicitly asked. Returns the id to poll with get_briefing.

입력 스키마

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟡create_source(name, description)

Create a new topic inbox: a themed container with its own dedicated email address (subscribe newsletters to it), which can hold RSS feeds and monitored web searches. This is how you add a whole new subject to someone's information diet.

입력 스키마

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Short name, e.g. \"AI research\" or \"Local news\""
    },
    "description": {
      "type": "string",
      "description": "Optional brief: what the reader expects from this inbox and what to skip — the editor reads it at every briefing"
    }
  },
  "required": [
    "name"
  ],
  "additionalProperties": false
}
🟡update_source(source_id, name, description, priority, include_in_digest, ...)

Change a topic inbox: rename it, change its description, raise or lower its priority in the briefing, set a per-inbox technicality level, temporarily exclude it from the briefing or pause it entirely.

입력 스키마

{
  "type": "object",
  "properties": {
    "source_id": {
      "type": "string",
      "description": "Id from list_sources"
    },
    "name": {
      "type": "string",
      "description": "New name for the inbox"
    },
    "description": {
      "type": "string",
      "description": "The inbox brief: what the reader expects from it and what to skip — the editor reads it at every briefing"
    },
    "priority": {
      "type": "integer",
      "minimum": 1,
      "maximum": 5,
      "description": "1 marginal … 5 always first"
    },
    "include_in_digest": {
      "type": "boolean",
      "description": "false = keep collecting but leave it out of the briefing"
    },
    "is_active": {
      "type": "boolean",
      "description": "false = stop collecting entirely"
    },
    "technicality": {
      "type": "integer",
      "minimum": 1,
      "maximum": 5,
      "description": "Override just for this inbox"
    }
  },
  "required": [
    "source_id"
  ],
  "additionalProperties": false
}
🔴delete_source(source_id)

Permanently delete a topic inbox with all its feeds, searches and collected content. Irreversible: the dedicated email address stops working too. Prefer update_source with is_active false when in doubt.

입력 스키마

{
  "type": "object",
  "properties": {
    "source_id": {
      "type": "string",
      "description": "Id from list_sources"
    }
  },
  "required": [
    "source_id"
  ],
  "additionalProperties": false
}
🟡add_feed(source_id, url)

Add an RSS/Atom feed to a topic inbox. You can pass the site address instead of the feed URL — the server fetches the page and discovers the feed. A podcast works too (its feed, its site, or an Apple Podcasts or Spotify link): it is followed as a podcast, and every new episode is transcribed and enters the briefing. If it fails, the reason is precise (blocked by the site, gone, unreadable) so it can be reported honestly.

입력 스키마

{
  "type": "object",
  "properties": {
    "source_id": {
      "type": "string",
      "description": "Which inbox (from list_sources)"
    },
    "url": {
      "type": "string",
      "description": "Feed URL or plain site address, e.g. \"ilpost.it\""
    }
  },
  "required": [
    "source_id",
    "url"
  ],
  "additionalProperties": false
}
🔴remove_feed(feed_id)

Remove an RSS feed from a topic inbox. Already-collected content stays; nothing new arrives from it.

입력 스키마

{
  "type": "object",
  "properties": {
    "feed_id": {
      "type": "string",
      "description": "Id from get_source"
    }
  },
  "required": [
    "feed_id"
  ],
  "additionalProperties": false
}
🟡add_web_search(source_id, query, kind)

Monitor a Google query every day and feed the results into a topic inbox: the standing-search way to follow a company, a person, a law or a niche subject that has no RSS feed. kind "news" watches the news index, "search" the whole web.

입력 스키마

{
  "type": "object",
  "properties": {
    "source_id": {
      "type": "string",
      "description": "Which inbox (from list_sources)"
    },
    "query": {
      "type": "string",
      "description": "The query, as you would type it into Google"
    },
    "kind": {
      "type": "string",
      "enum": [
        "news",
        "search"
      ],
      "description": "Default news"
    }
  },
  "required": [
    "source_id",
    "query"
  ],
  "additionalProperties": false
}
🔴remove_web_search(search_id)

Stop monitoring a standing web search: no new results from that query will reach the briefing. What it already collected stays where it is.

입력 스키마

{
  "type": "object",
  "properties": {
    "search_id": {
      "type": "string",
      "description": "Id from get_source"
    }
  },
  "required": [
    "search_id"
  ],
  "additionalProperties": false
}
🟢discover_sources(source_id, description)

Describe a subject in plain words and get back real, working sources for it: RSS feeds validated live by the server (dead ones are dropped before you see them), web searches worth monitoring, and newsletters worth subscribing to. Nothing is added — it returns proposals to pass to add_feed / add_web_search.

입력 스키마

{
  "type": "object",
  "properties": {
    "source_id": {
      "type": "string",
      "description": "The inbox the proposals are for (its existing sources are excluded)"
    },
    "description": {
      "type": "string",
      "description": "What they want to follow, in plain words"
    }
  },
  "required": [
    "source_id",
    "description"
  ],
  "additionalProperties": false
}
🟡import_opml(source_id, opml, dry_run, limit)

Import subscriptions from another RSS reader (Feedly, Inoreader, FreshRSS, NetNewsWire) by passing the OPML file contents. Set dry_run true first to see what is in it and what is already present; then run it for real to add them (they are validated one by one, and the ones that fail come back with the reason).

입력 스키마

{
  "type": "object",
  "properties": {
    "source_id": {
      "type": "string",
      "description": "Which inbox to import into"
    },
    "opml": {
      "type": "string",
      "description": "The full OPML/XML file contents"
    },
    "dry_run": {
      "type": "boolean",
      "description": "true = only list what would be imported"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 40,
      "description": "Max feeds to add in this call (default 20 — big imports go in batches)"
    }
  },
  "required": [
    "source_id",
    "opml"
  ],
  "additionalProperties": false
}
🔴unsubscribe_newsletter(newsletter_id)

Unsubscribe from a newsletter arriving in one of the inboxes. When the sender supports one-click unsubscribe the server does it directly; otherwise it returns the URL a human has to open, and says so honestly.

입력 스키마

{
  "type": "object",
  "properties": {
    "newsletter_id": {
      "type": "string",
      "description": "Id from get_source (newsletters)"
    }
  },
  "required": [
    "newsletter_id"
  ],
  "additionalProperties": false
}

커뮤니티

이 서버 평가하기

증거

최근 관측

검증됨버전이 기록되지 않음도구 47개
검증됨버전이 기록되지 않음도구 40개
검증됨버전이 기록되지 않음도구 40개
검증됨버전이 기록되지 않음도구 40개
검증됨버전이 기록되지 않음도구 28개
검증됨버전이 기록되지 않음도구 28개
검증됨버전이 기록되지 않음도구 28개