Skip to main content
Glama

proofite

by com.proofite
OverviewDiscussionsAdmin

Change how the briefing is written

update_information_diet
Idempotent

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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toneNocome deve scrivere («diretto, zero fuffa»)
avoidNocosa non vuole leggere mai
depthNo1 solo i fatti … 5 analisi e implicazioni
stanceNo1 neutro … 5 l'editor si sbilancia
languageNolingua del briefing e del podcast
timezoneNofuso orario IANA (Europe/Rome)
entry_mixNo1 poche voci trattate a fondo … 5 tante voci brevi (la lunghezza totale non cambia)
interestsNocosa seguire, in linguaggio naturale
digest_daysNogiorni della settimana, ISO 1=lunedì … 7=domenica
digest_timeNoorario di consegna, HH:MM nel fuso dell'utente
technicalityNo1 divulgativo … 5 da addetti ai lavori
digest_lengthNoquanto deve essere lungo
serper_enrichNoarricchire il briefing con ricerche web fresche
chicca_enabledNonei giorni senza notizie, una storia vera dall'archivio
digest_enabledNoricevere o meno il briefing quotidiano
podcast_accentoNoaccento 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
podcast_enabledNogenerare anche l'episodio audio
podcast_formatoNoshow = due conduttori che si rispondono (il formato di casa); classico = una voce che legge il briefing
podcast_minutesNodurata desiderata dell'episodio
email_digest_enabledNoricevere il briefing anche per email
smalltalking_enabledNoogni giorno, in coda al briefing, due o tre storie brevi da raccontare
weekly_recap_enabledNoriepilogo settimanale di ciò che non è stato letto

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / podcast_accento / description
      Previous value: -"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)"New value: +"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"
    • changedInput schema / properties / podcast_accento / enum
      Previous value: -[
-  "us",
-  "gb",
-  "au",
-  "ie",
-  "in",
-  "es",
-  "latam",
-  "fr",
-  "ca",
-  "de",
-  "at",
-  "ch"
-]New value: +[
+  "us",
+  "gb",
+  "au",
+  "ie",
+  "in",
+  "es",
+  "latam",
+  "fr",
+  "ca",
+  "de",
+  "at",
+  "ch",
+  null
+]
    • changedInput schema / properties / podcast_accento / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / podcast_accento
      Added value: +{
+  "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)",
+  "enum": [
+    "us",
+    "gb",
+    "au",
+    "ie",
+    "in",
+    "es",
+    "latam",
+    "fr",
+    "ca",
+    "de",
+    "at",
+    "ch"
+  ],
+  "type": "string"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / podcast_formato
      Added value: +{
+  "description": "show = due conduttori che si rispondono (il formato di casa); classico = una voce che legge il briefing",
+  "enum": [
+    "show",
+    "classico"
+  ],
+  "type": "string"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / entry_mix
      Added value: +{
+  "description": "1 poche voci trattate a fondo … 5 tante voci brevi (la lunghezza totale non cambia)",
+  "maximum": 5,
+  "minimum": 1,
+  "type": "integer"
+}
  5. Changed1 schema field changed
    • addedInput schema / properties / smalltalking_enabled
      Added value: +{
+  "description": "ogni giorno, in coda al briefing, due o tre storie brevi da raccontare",
+  "type": "boolean"
+}
  6. First observed

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare mutating (readOnlyHint=false), idempotent, non-destructive. The description adds partial-update semantics ('Pass only the keys you want to change') and the global-scope constraint, which are not captured by annotations. However, it doesn't describe return behavior or merge semantics in detail; given annotation coverage, 4 is appropriate.

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 purpose and a thematic enumeration, followed by two crisp operational sentences. The long enumeration overlaps with the schema but aids selection; overall structure is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 22-parameter mutation tool with no output schema, the description plus annotations and schema cover purpose, usage, and safety. It could mention return values but that is minor; the definition is sufficient for correct invocation.

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 description coverage is 100%, so the schema already documents all 22 parameters thoroughly. The description's prose enumeration adds grouping (podcast, email) but no syntax or format details beyond the schema, 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?

States a specific verb 'Change' and resource 'how and when the briefing reaches this person', enumerates the settings covered, and distinguishes itself from siblings by naming get_information_diet and tune_topic. An agent can identify scope without opening the schema.

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 instructs to read get_information_diet first, to pass only keys to change, and clarifies these are global settings not per-topic, routing to tune_topic for single topics. Covers when-to-use, prerequisites, and alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All proofite toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources