com.shotpulled/shotpulled

Est-ce que com.shotpulled/shotpulled est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.shotpulled/shotpulled » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 44 outils

• compute_age≈ 309 tokens

  Compute a bag's age in days off roast and its resting/staling verdict — the coffee's current bag by default, or the bag named.

  Paramètres, retour & exemple (2)

  Paramètres

  • bag_id · integer|null · optionnel
    A bag of that coffee (from list_beans' bags[]); null = its current bag
  • bean_id · integer · requis

  Exemple d'appel

  {"name": "compute_age", "arguments": {"bean_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"bag_id": 1, "bean_id": 1, "verdict": "texte", "age_days": 1, "warnings": [], "roast_date": "texte", "rest_window": "texte", "days_off_roast": 1, "grams_remaining": "texte", "days_since_opened": "texte", "effective_age_days": 1, "frozen_days_excluded": 1}}

• delete_shot≈ 199 tokens

  Delete a logged shot from history. Restores the bean's remaining weight (which is derived from logged doses). Hard delete — there is no undo. To fix a mistake on an otherwise-valid shot, prefer update_shot over delete-and-relog.

  Paramètres, retour & exemple (1)

  Paramètres

  • shot_id · integer · requis
    ID of the shot to delete

  Exemple d'appel

  {"name": "delete_shot", "arguments": {"shot_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "message": "texte", "deleted_shot_id": 1}}

• diagnose_preview≈ 797 tokens

  Sandbox-only diagnosis, writes nothing (no verdict, no recommendation-trail entry). Two modes: pass shot_id to dry-run a LOGGED shot (optionally overriding its sensory_tags — the "what would this read as?" preview; the shot's own bean and its age at pulled_at are used), or pass the full metric set (bean_id, grinder_id, machine_id, grind_label, dose_g, yield_g, time_s, source) for a hypothetical shot. Identical output shape to diagnose_shot, including bean_context.

  Paramètres, retour & exemple (10)

  Paramètres

  • dose_g · number · optionnel
    Dose in grams
  • source · string · optionnel · measured | recalled | assumed
    Grinder position source — affects G1 warning (raw mode only)
  • time_s · number · optionnel
    Extraction time in seconds
  • bean_id · integer · optionnel
    Coffee bean ID (must belong to this account)
  • shot_id · integer · optionnel
    Preview a logged shot by ID (dry-run; ignores the metric params below)
  • yield_g · number · optionnel
    Yield in grams
  • grinder_id · integer · optionnel
    Grinder ID (must belong to this account)
  • machine_id · integer · optionnel
    Machine ID (must belong to this account)
  • grind_label · string · optionnel
    Grinder setting label, e.g. "1.1.3"
  • sensory_tags · array · optionnel
    Sensory observations, e.g. ["sour","bitter"]. With shot_id: replaces the stored tags for this preview (omit to use stored; [] = none).

  Exemple d'appel

  {"name": "diagnose_preview", "arguments": {"dose_g": 1, "source": "measured", "time_s": 1, "bean_id": 1, "shot_id": 1, "yield_g": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"facts": [], "category": "texte", "warnings": [], "hypotheses": [], "kb_version": "texte", "bean_context": {}, "one_variable_only": true}}

• diagnose_shot≈ 571 tokens

  Evaluate shot metrics to provide ranked hypotheses (C6) and warn on flip-flops (G2) or fatigue (G6). Resolves the SHOT's own bean — age computed at the shot's pulled_at — never the active profile, and echoes it as bean_context, so diagnosing an older or differently-filed shot is always safe. The engine reads metrics and sensory tags — NOT free-text notes — so make sure taste feedback is recorded as sensory_tags on the shot (via log_shot or update_shot) before diagnosing; otherwise an in-range shot that tastes bad will come back "balanced".

  Paramètres, retour & exemple (1)

  Paramètres

  • shot_id · integer · optionnel
    Optional shot ID; defaults to last pulled shot.

  Exemple d'appel

  {"name": "diagnose_shot", "arguments": {"shot_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"facts": [], "category": "texte", "warnings": [], "hypotheses": [], "kb_version": "texte", "bean_context": {}, "one_variable_only": true}}

• get_dial_state≈ 2931 tokens

  Retrieve current dialing state, active context, recent shots, recommendations, and locked recipes.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_dial_state", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"recent_shots": [], "active_coffee": {}, "locked_recipe": {}, "active_grinder": {}, "active_machine": {}, "active_program": "texte", "maintenance_summary": {}, "recent_recommendations": []}}

• get_kb_version≈ 111 tokens

  Retrieve the current version of the knowledge base.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_kb_version", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"kb_version": "texte"}}

• get_maintenance_guides≈ 847 tokens

  Step-by-step maintenance guides — tools, supplies, steps and warnings, in our own words with the maker's documents as sources. With no arguments, every guide for the user's current grinders and machines (and the water filter fitted in each). With guide_ids, those guides; the ids come from maintenance.tasks[].guide.id in list_grinders and list_machines. Ids that match no guide are listed under missing.

  Paramètres, retour & exemple (1)

  Paramètres

  • guide_ids · array · optionnel
    Optional — the guides to fetch. Omit for every guide the user's equipment can use

  Exemple d'appel

  {"name": "get_maintenance_guides", "arguments": {"guide_ids": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"guides": [], "missing": "texte", "catalog_version": "texte"}}

• get_rule≈ 152 tokens

  Retrieve the detailed text of a specific rule from the knowledge base by its rule ID.

  Paramètres, retour & exemple (1)

  Paramètres

  • rule_id · string · requis
    The ID of the rule to fetch, e.g. CAT.DARK

  Exemple d'appel

  {"name": "get_rule", "arguments": {"rule_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"text": "texte", "rule_id": "texte"}}

• get_stats≈ 230 tokens

  Get compact flat usage stats for a grinder, machine, or bean.

  Paramètres, retour & exemple (2)

  Paramètres

  • id · integer · requis
    The entity ID
  • scope · string · requis · grinder | machine | bean
    The stats scope

  Exemple d'appel

  {"name": "get_stats", "arguments": {"id": 1, "scope": "grinder"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"brews": 1, "last_bean": "texte", "last_used": "texte", "grams_ground": 1, "effective_age": 1, "beans_consumed": 1, "grams_consumed": 1, "grams_remaining": 1, "last_grind_setting": "texte"}}

• grinder_math≈ 210 tokens

  Determine steps/clicks difference and directions between setting labels (C3).

  Paramètres, retour & exemple (3)

  Paramètres

  • to_label · string · requis
  • from_label · string · requis
  • grinder_id · integer · requis

  Exemple d'appel

  {"name": "grinder_math", "arguments": {"to_label": "texte", "from_label": "texte", "grinder_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"steps": 1, "direction": "texte", "step_unit": "texte", "burr_gap_travel_microns": 1, "relative_coarseness_note": "texte"}}

• kb_changelog≈ 118 tokens

  Retrieve the changelog showing updates and version differences for the knowledge base.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "kb_changelog", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"changelog": "texte"}}

• list_beans≈ 1322 tokens

  List the coffees registered for the account, with status filter. Each coffee carries its bags[] (every purchase, with its own freshness and grams left) and current_bag_id; the row's top-level roast_date, state, grams_remaining and age fields are the current bag's. The `id` on each row is the number this account knows that coffee by, counting from 1 — safe to show, and what other tools expect back; bag ids are a separate series.

  Paramètres, retour & exemple (1)

  Paramètres

  • status · string · optionnel · current | archived | all
    Filter by status: current, archived, or all. Defaults to current.

  Exemple d'appel

  {"name": "list_beans", "arguments": {"status": "current"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"beans": []}}

• list_grinders≈ 2250 tokens

  List grinders registered for the account, with status filter. The `id` on each row is the number this account knows that record by, counting from 1 — safe to show, and what other tools expect back. Each row carries its maintenance block: every task with its class (S schedule, H habit, Y symptom, A the machine signals it, T technician, N never, U unstated, E event), due state, and the guide to follow.

  Paramètres, retour & exemple (2)

  Paramètres

  • status · string · optionnel · current | archived | all
    Filter by status: current, archived, or all. Defaults to current.
  • maintenance · string · optionnel · compact | full
    How much of each row's maintenance block to include. compact (default): every task with its class, due state, schedule and guide. full: also the maker's own words — quote, source, alternates, the interval as written.

  Exemple d'appel

  {"name": "list_grinders", "arguments": {"status": "current", "maintenance": "compact"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"grinders": []}}

• list_machines≈ 2568 tokens

  List machines registered for the account, with status filter. The `id` on each row is the number this account knows that record by, counting from 1 — safe to show, and what other tools expect back. Each row carries its maintenance block, researched per model: every task with its class, due state, what the maker forbids, and the guide to follow. `settings` lists the selectors its model has and where each stands (null: unknown model, or none).

  Paramètres, retour & exemple (2)

  Paramètres

  • status · string · optionnel · current | archived | all
    Filter by status: current, archived, or all. Defaults to current.
  • maintenance · string · optionnel · compact | full
    How much of each row's maintenance block to include. compact (default): every task with its class, due state, schedule and guide. full: also the maker's own words — quote, source, alternates, the interval as written.

  Exemple d'appel

  {"name": "list_machines", "arguments": {"status": "current", "maintenance": "compact"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"machines": []}}

• list_maintenance_due≈ 561 tokens

  What maintenance is due across the user's current grinders and machines, most urgent first — for "is anything due?". Only tasks with an interval compete: a task the machine counts and signals itself, one done by habit or when a symptom shows, and one the maker advises against never appear. Each item says how far along it is (ratio, done of every, on which basis), whether it is coming up (soon), and whether the interval is the user's, the maker's or ShotPulled's default.

  Paramètres, retour & exemple (1)

  Paramètres

  • status · string · optionnel · due | all
    due (default): due or overdue, and not muted. all: every scheduled task, muted ones last

  Exemple d'appel

  {"name": "list_maintenance_due", "arguments": {"status": "due"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"items": [], "computed_at": "texte", "catalog_version": "texte"}}

• list_recipes≈ 584 tokens

  List recipes (all or filtered by equipment and status). The `id` on each row is the number this account knows that record by, counting from 1 — safe to show, and what other tools expect back.

  Paramètres, retour & exemple (4)

  Paramètres

  • status · string · optionnel · current | archived | all
    Filter by status: current, archived, or all. Defaults to current.
  • bean_id · integer · optionnel
  • grinder_id · integer · optionnel
  • machine_id · integer · optionnel

  Exemple d'appel

  {"name": "list_recipes", "arguments": {"status": "current", "bean_id": 1, "grinder_id": 1, "machine_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"recipes": []}}

• list_scales≈ 356 tokens

  List registered scales for the account. The `id` on each row is the number this account knows that record by, counting from 1 — safe to show, and what other tools expect back.

  Paramètres, retour & exemple (1)

  Paramètres

  • status · string · optionnel · current | archived | all
    Filter by status: current (unarchived), archived, or all. Defaults to current.

  Exemple d'appel

  {"name": "list_scales", "arguments": {"status": "current"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"scales": []}}

• list_shots≈ 897 tokens

  List shot history with support for pagination and filtering. Every shot carries a derived taste_pending flag (1 = logged with no sensory tags, no rating, and no tasted flip — the tasting is still owed and can be backfilled with update_shot).

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    Number of records to return (1-500)
  • offset · integer · optionnel
    Offset for pagination
  • filters · object · optionnel

  Exemple d'appel

  {"name": "list_shots", "arguments": {"limit": 1, "offset": 1, "filters": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"shots": [], "total": 1}}

• list_waters≈ 281 tokens

  List registered waters for the account. The `id` on each row is the number this account knows that record by, counting from 1 — safe to show, and what other tools expect back.

  Paramètres, retour & exemple (1)

  Paramètres

  • status · string · optionnel · current | archived | all
    Filter by status: current (unarchived), archived, or all. Defaults to current.

  Exemple d'appel

  {"name": "list_waters", "arguments": {"status": "current"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"waters": []}}

• lock_recipe≈ 205 tokens

  Lock a successful shot as the reference dialing recipe for this equipment profile. It overwrites the recipe already locked for the same coffee, grinder, machine, program and drink intent, which keeps its recipe_id.

  Paramètres, retour & exemple (2)

  Paramètres

  • drink_intent · string · requis · straight | milk
  • from_shot_id · integer · requis

  Exemple d'appel

  {"name": "lock_recipe", "arguments": {"drink_intent": "straight", "from_shot_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "message": "texte", "recipe_id": 1}}

• log_maintenance≈ 1199 tokens

  Log a cleaning or maintenance job against a piece of equipment. A task that takes the thing apart opens a calibration epoch, and every recipe locked before it is read through that epoch's offset — so record the offset here if you counted the clicks while reassembling, which is the one moment anybody actually knows it. Any task in the maintenance vocabulary can be logged against a grinder or machine it belongs to — including one the maker advises against, because the log records what was done. Read each piece of equipment's tasks, their intervals and their due state from list_grinders and list_machines.

  Paramètres, retour & exemple (11)

  Paramètres

  • note · string · optionnel
    Optional — what you did, and anything that surprised you
  • task · string · requis · burr_clean | backflush_water | backflush_detergent | descale | group_gasket_replace | shower_screen_clean | shower_screen_replace | group_head_wipe
    Which maintenance job was performed
  • details · object · optionnel
    Fields specific to this task. Which ones a task takes is published as details_fields on each task; a burr clean takes none
  • evidence · string · optionnel
    One line recording what the measurement rested on, e.g. "Counted 6 clicks coarser at reassembly."
  • guide_id · string · optionnel
    Optional — the id of the maintenance guide that was followed. Must be a guide for this task
  • equipment_id · integer · requis
    The ID of that piece of equipment
  • offset_value · number · optionnel
    The correction, if you measured it now: clicks to ADD to a pre-clean reading to get the same grind today, signed along the collar's own number direction. Omit it and the epoch stays unmeasured, which is a state the app shows rather than a zero it assumes
  • performed_at · string · optionnel
    When it was done (ISO 8601 or YYYY-MM-DD HH:MM:SS, UTC). Defaults to now; backdating is fine
  • disturbs_zero · integer · optionnel · 0 | 1
    Whether this job disturbed the reference the stored numbers are read against — for a burr clean, whether the burrs actually came out. Defaults to the task's own answer; send 0 for a wipe-down that left the collar alone
  • offset_source · string · optionnel · pull | counted | typed
    How the offset was arrived at: pull (a reference shot), counted (clicks counted at reassembly), typed (asserted directly)
  • equipment_kind · string · requis · grinder | machine
    Which kind of equipment this job was done on

  Exemple d'appel

  {"name": "log_maintenance", "arguments": {"task": "burr_clean", "equipment_id": 1, "equipment_kind": "grinder"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"entry": {}, "deduped": true, "message": "texte", "entry_id": 1}}

• log_recommendation≈ 238 tokens

  Log a recommended dialing change to allow contradiction/oscillation checking (G2).

  Paramètres, retour & exemple (6)

  Paramètres

  • lever · string · requis · grind | yield | temp | program | prep | none
  • direction · string · requis · finer | coarser | more | less | same
  • rationale · string · requis
  • confidence · string · requis · low | medium | high
  • cited_rules · array · optionnel
  • based_on_shot · integer · optionnel

  Exemple d'appel

  {"name": "log_recommendation", "arguments": {"lever": "grind", "direction": "finer", "rationale": "texte", "confidence": "low"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "message": "texte"}}

• log_shot≈ 1244 tokens

  Log an espresso or alternative shot/brew attempt. Uses the active context (bean/grinder/machine/program) unless overridden via bean_id/grinder_id/machine_id/program_id — ALWAYS pass bean_id explicitly when the user names a specific coffee, so the shot cannot land on the wrong bag. Backdate with pulled_at when the shot happened earlier. When the user reports taste (bitter, sour, harsh, hollow…), include matching sensory_tags — the diagnosis engine reads tags and metrics, not free-text flavor_notes. When the user tasted the shot and reports it as GOOD/clean (no defects), pass tasted=1 with no sensory_tags — otherwise a tag-less, rating-less shot is filed taste-pending as if never tasted.

  Paramètres, retour & exemple (33)

  Paramètres

  • tds · number · optionnel
    Total Dissolved Solids percentage (e.g. 9.1 or 1.35)
  • bag_id · integer|null · optionnel
    Which bag of the coffee the shot came from; defaults to its current (open) bag. Bag numbers are on list_beans' bags[]
  • dose_g · number · requis
  • rating · integer · optionnel
  • tasted · integer · optionnel · 0 | 1
    1 = the shot was tasted at log time. The explicit way to record a CLEAN tasting: sensory tags all describe defects, so a good shot has none — without this flag (or a rating) it would be filed taste-pending. Tags or a rating also mark a shot as tasted; 0 (default) = taste later.
  • time_s · number · requis
  • bean_id · integer|null · optionnel
    Override: log against this bean instead of the active one (null = active)
  • verdict · string · optionnel
  • yield_g · number · requis
  • water_id · integer · optionnel
    Optional references to waters formulation
  • best_brew · integer · optionnel · 0 | 1
    1 if marked as best brew, 0 otherwise
  • favourite · integer · optionnel · 0 | 1
    1 if favourite, 0 otherwise
  • pulled_at · string|null · optionnel
    When the shot was actually pulled (ISO 8601 or "YYYY-MM-DD HH:MM:SS"), for backdated entries. Defaults to now (null = now). When backdating, pass the returned shot_id to diagnose_shot explicitly — the default diagnosis target is the chronologically latest shot.
  • beverage_g · number · optionnel
    Yield mass excluding cup/vessel weight in grams
  • grinder_id · integer|null · optionnel
    Override: grinder used, if not the active one (null = active)
  • machine_id · integer|null · optionnel
    Override: machine used, if not the active one (null = active)
  • program_id · integer|null · optionnel
    Override: machine program used, if not the active one (null = active)
  • temp_taste · string · optionnel · hot | warm | cold
  • vessel_name · string · optionnel
    Cup/vessel name
  • bloom_time_s · number · optionnel
    Pre-wetting or bloom duration in seconds
  • drink_intent · string · optionnel · straight | milk
  • flavor_notes · string · optionnel
  • flow_profile · string · optionnel
    Opaque flow profile data (JSON/TEXT)
  • method_tools · string · optionnel
    JSON representation of method tools used (e.g., paper filters, screen)
  • observations · object · optionnel
  • sensory_tags · array · optionnel
  • finish_action · string · requis · hard_stop | passive_drip
  • temperature_c · number · optionnel
    Brew temperature in Celsius
  • data_confidence · string · optionnel · measured | recalled | estimated
    measured = weighed/timed live; recalled = from memory; estimated = a best guess (e.g. missed the timer — "~25s")
  • vessel_weight_g · number · optionnel
    Cup/vessel weight in grams
  • machine_settings · object · optionnel
    Only when this one shot was pulled with a selector somewhere other than the machine's recorded settings: {key: position}. The shot is otherwise stamped with those automatically; a lasting change goes through update_machine.
  • pressure_profile · string · optionnel
    Pressure profile description or values
  • first_drip_time_s · number · optionnel
    Time to first drip in seconds

  Exemple d'appel

  {"name": "log_shot", "arguments": {"dose_g": 1, "time_s": 1, "yield_g": 1, "finish_action": "hard_stop"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "message": "texte", "shot_id": 1}}

• merge_beans≈ 438 tokens

  Fold one coffee into another when the same coffee was registered twice. Every bag, shot, recipe and recommendation of from_bean_id moves to into_bean_id; the active coffee follows if it was the one merged away; origins move only if the target has none. Where both hold a locked recipe for the same grinder, machine, program and drink, the newer lock wins and the older is deleted. The source coffee is archived, never deleted. Irreversible — confirm both numbers with the user first (list_beans shows them).

  Paramètres, retour & exemple (3)

  Paramètres

  • reason · string · optionnel
    Optional note, recorded on the surviving coffee's notes with the merge
  • from_bean_id · integer · requis
    The duplicate: the coffee number that will be emptied and archived
  • into_bean_id · integer · requis
    The coffee number that keeps everything

  Exemple d'appel

  {"name": "merge_beans", "arguments": {"from_bean_id": 1, "into_bean_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"moved": {}, "status": "texte", "message": "texte", "into_bean_id": 1, "active_followed": true, "replaced_recipes": 1}}

• register_bag≈ 520 tokens

  Register another bag of a coffee that is already in list_beans — the same roaster's product, bought again. It keeps the coffee's recipes, notes and history; only the purchase facts (roast date, weight, price, state) are new. Does not change the active coffee. Returns a bag_id: bag numbers are their own series, separate from bean numbers. For a coffee that is not in list_beans yet, call register_coffee instead.

  Paramètres, retour & exemple (13)

  Paramètres

  • ean · string · optionnel
  • cost · number · optionnel
  • state · string · optionnel · sealed | open | frozen | finished
    Defaults to sealed; the first log_shot against it opens it
  • bean_id · integer · requis
    This account's own coffee number, from list_beans. Never guess one.
  • qr_code · string · optionnel
  • storage · string · optionnel
  • buy_date · string · optionnel
    Calendar day in YYYY-MM-DD format — a day, not a timestamp
  • currency · string · optionnel
  • bag_notes · string · optionnel
    Notes about THIS bag (a batch note, where it was bought). The coffee's own description lives on the coffee, in notes.
  • roast_date · string · requis
    Calendar day in YYYY-MM-DD format — a day, not a timestamp
  • opened_date · string · optionnel
    Calendar day in YYYY-MM-DD format — a day, not a timestamp
  • bag_weight_g · number · optionnel
    Bag weight in grams
  • best_by_date · string · optionnel
    Calendar day in YYYY-MM-DD format — a day, not a timestamp

  Exemple d'appel

  {"name": "register_bag", "arguments": {"bean_id": 1, "roast_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"bag_id": 1, "status": "texte", "bean_id": 1, "message": "texte"}}

• register_coffee≈ 1319 tokens

  Register a coffee that is NOT yet in list_beans, together with its first bag. It does not switch a coffee in use: it becomes active only when no coffee is in use (none active, or the active one archived or with every bag finished); otherwise call set_active with its bean_id when the user starts brewing it. The `active` field of the reply says which. The coffee is the roaster's product (roaster, origins, variety, process, roast level, roasting type, cupping score, aromatics, roaster notes, rest window); the bag is this purchase (roast date, weight, price, state). For another bag of a coffee already on file call register_bag instead — it keeps the recipes and notes. Returns bean_id and the first bag's bag_id.

  Paramètres, retour & exemple (45)

  Paramètres

  • ean · string · optionnel
  • url · string · optionnel
  • body · string · optionnel
    Free text; roasters usually say low, medium or high
  • cost · number · optionnel
  • name · string · requis
  • notes · string · optionnel
    The coffee's own description — the roaster's tasting notes, the dialing approach that worked. Per bag notes go in bag_notes.
  • state · string · optionnel · sealed | open | frozen | finished
  • origin · string · optionnel
  • rating · integer · optionnel
  • acidity · string · optionnel
    Free text; roasters usually say low, medium or high
  • co2e_kg · number · optionnel
  • origins · array · optionnel
    List of bean origin details
  • qr_code · string · optionnel
  • roaster · string · optionnel
  • storage · string · optionnel
  • variety · string · optionnel
  • archived · integer · optionnel
    1 if archived, 0 otherwise
  • bean_mix · string · optionnel
    E.g. blend details
  • buy_date · string · optionnel
    Calendar day in YYYY-MM-DD format — a day, not a timestamp
  • currency · string · optionnel
  • finished · integer · optionnel
    1 if finished, 0 otherwise
  • aromatics · string · optionnel
  • bag_notes · string · optionnel
  • favourite · integer · optionnel
    1 if favourite, 0 otherwise
  • frozen_at · string · optionnel
    Calendar day the bag went into the freezer, YYYY-MM-DD — a day, not a timestamp
  • sweetness · string · optionnel
    Free text; roasters usually say low, medium or high
  • roast_date · string · requis
    Calendar day in YYYY-MM-DD format — a day, not a timestamp
  • arabica_pct · number · optionnel
    Percent arabica, 100 for a pure arabica; the rest robusta
  • attachments · string · optionnel
    JSON or comma-separated list of attachments
  • frozen_note · string · optionnel
  • opened_date · string · optionnel
    Calendar day in YYYY-MM-DD format — a day, not a timestamp
  • roast_level · string · requis · ultra-light | light | medium | medium-dark | dark
  • roast_range · string · optionnel
  • unfrozen_at · string · optionnel
    Calendar day the bag came out, YYYY-MM-DD — a day, not a timestamp
  • bag_weight_g · number · optionnel
    Bag weight in grams
  • best_by_date · string · optionnel
    Calendar day in YYYY-MM-DD format — a day, not a timestamp
  • process_type · string · requis · washed | natural | honey | anaerobic | aerobic-extended | co-fermented | bioreactor | other
  • roast_custom · string · optionnel
  • decaffeinated · integer · optionnel
    1 if decaf, 0 if regular
  • dial_category · string · optionnel · nordic-light | ultra-light | classic | processed | dark | aged
    Dialing behavior class: classic = medium/traditional espresso roasts (chocolate/nut, balanced); dark = genuinely dark/roasty; the light categories cover Nordic and ultra-light styles.
  • roasting_type · string · optionnel · filter | espresso | omni
  • cupping_points · number · optionnel
  • frozen_storage · string · optionnel
  • rest_window_days_max · integer · optionnel
  • rest_window_days_min · integer · optionnel

  Exemple d'appel

  {"name": "register_coffee", "arguments": {"name": "texte", "roast_date": "texte", "roast_level": "ultra-light", "process_type": "washed"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"active": true, "bag_id": 1, "status": "texte", "bean_id": 1, "message": "texte"}}

• register_grinder≈ 620 tokens

  Register a manual or electric grinder with its dial settings scheme. It becomes the active grinder only when no grinder is in use (none active, or the active one archived); otherwise call set_active with its grinder_id to switch to it. The `active` field of the reply says which.

  Paramètres, retour & exemple (14)

  Paramètres

  • name · string · requis
    The name/model of the grinder, e.g. Kinu M47
  • notes · string · optionnel
    Additional notes
  • photo · string · optionnel
    Photo path or URL
  • archived · integer · optionnel
    1 if archived, 0 if active
  • burr_type · string · requis · conical | flat
  • max_value · number|null · optionnel
    Optional travel max bounds
  • min_value · number|null · optionnel
    Optional travel min bounds
  • catalog_id · string · optionnel
    Optional — the maintenance catalog model this is (the `id` of a catalog row, e.g. rancilio-silvia), when it was registered from the catalog. Its maintenance then comes from that model's researched record. "none" says it is not in the catalog.
  • motor_type · string · requis · manual | electric
  • nominal_step · number · requis
    Smallest adjustment increment (e.g. 1 click or 0.1collar units)
  • setting_scheme · string · requis · numeric_stepless | numeric_stepped | clicks_single | compound | named
    Collar mark style: single clicks or compound (rotation.number.clicks)
  • components_spec · string · optionnel
    JSON mapping string representing compound adjustment math
  • microns_per_step · number|null · optionnel
    Optional mechanical burr travel microns per nominal step
  • direction_convention · string · requis · lower_is_finer | higher_is_finer

  Exemple d'appel

  {"name": "register_grinder", "arguments": {"name": "texte", "burr_type": "conical", "motor_type": "manual", "nominal_step": 1, "setting_scheme": "numeric_stepless", "direction_convention": "lower_is_finer"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"active": true, "status": "texte", "message": "texte", "grinder_id": 1}}

• register_machine≈ 658 tokens

  Register an espresso or alternative preparation machine. It becomes the active machine only when no machine is in use (none active, or the active one archived); otherwise call set_active with its machine_id to switch to it. The `active` field of the reply says which.

  Paramètres, retour & exemple (14)

  Paramètres

  • name · string · requis
    Machine name/model, e.g. Dedica EC685
  • notes · string · optionnel
  • photo · string · optionnel
    Photo path or URL
  • tools · string|null · optionnel
    JSON or comma-separated tools, e.g., paper filters, flow control, metal mesh
  • archived · integer · optionnel
    1 if archived, 0 if active
  • prep_type · string · optionnel
    Preparation equipment type. One of: espresso_machine, lever_press, moka_pot, aeropress, french_press, v60_dripper, cold_brew. Lower snake_case.
  • catalog_id · string · optionnel
    Optional — the maintenance catalog model this is (the `id` of a catalog row, e.g. rancilio-silvia), when it was registered from the catalog. Its maintenance then comes from that model's researched record. "none" says it is not in the catalog.
  • prep_style · string · optionnel
    Preparation style. One of: espresso, filter, immersion, percolation. Only "espresso" is diagnosed by the dialing engine (G8) — anything else is recorded but never dialed, so do not guess this field.
  • boiler_type · string · optionnel
  • hardness_dh · number|null · optionnel
    Optional — the TOTAL hardness (GH) of the water this machine runs on, in °dH (German degrees; ppm as CaCO3 ÷ 17.85), as a test strip reports it. Picks the band of a maker's hardness table for descaling and filter life
  • control_type · string · requis · volumetric | manual | lever
  • connected_device · string · optionnel
    Metadata mapping to smart hardware APIs
  • basket_size_grams · number · optionnel
  • built_in_grinder_id · integer · optionnel
    id of a grinder built into this machine (bean-to-cup / integrated grinder)

  Exemple d'appel

  {"name": "register_machine", "arguments": {"name": "texte", "control_type": "volumetric"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"active": true, "status": "texte", "message": "texte", "machine_id": 1}}

• register_program≈ 410 tokens

  Register a programmed shot button on a machine. A program cuts the shot off either by weight (program_type "volumetric", set target_volume_g) or by time (program_type "timed", set target_time_s). One machine can have a mix of both. A program_number the machine already has is overwritten with these settings; shots logged on it keep pointing at it.

  Paramètres, retour & exemple (7)

  Paramètres

  • machine_id · integer · requis
  • description · string|null · optionnel
  • program_type · string · optionnel · volumetric | timed
    Cutoff method: "volumetric" (weight) or "timed" (duration). Defaults to volumetric.
  • target_time_s · number|null · optionnel
    Target shot duration cutoff in seconds (required for timed programs)
  • volume_source · string · optionnel · measured | recalled
    Confidence in the stored cutoff value, for either type
  • program_number · integer · requis
    Program number / button index (e.g. 1 or 2)
  • target_volume_g · number|null · optionnel
    Target yield cutoff in grams (required for volumetric programs)

  Exemple d'appel

  {"name": "register_program", "arguments": {"machine_id": 1, "program_number": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "message": "texte", "program_id": 1}}

• register_scale≈ 685 tokens

  Register a brewing scale — the instrument that weighs the dose and the yield.

  Paramètres, retour & exemple (15)

  Paramètres

  • name · string · requis
    Scale name/model, e.g. Acaia Lunar, Timemore Black Mirror Basic 2
  • notes · string · optionnel
    Additional notes
  • power · string · optionnel · usb_c | micro_usb | aa | aaa | mains
    How it is powered or recharged
  • depth_mm · number|null · optionnel
    Platform depth in mm
  • width_mm · number|null · optionnel
    Platform width in mm — measure your drip tray
  • auto_tare · integer|null · optionnel
    1 if it zeroes itself when a vessel is set down, 0 if not, null if unstated
  • height_mm · number|null · optionnel
    Overall height in mm — the dimension that decides whether it fits under a group head
  • auto_timer · integer|null · optionnel
    1 if the timer starts on first flow, 0 if not, null if unstated
  • capacity_g · number|null · optionnel
    Maximum weight in grams. The cup or portafilter counts against it
  • scale_type · string · requis · espresso | brew | dual | connected | dosing | training | bench
    What the scale is built for: espresso (drip-tray footprint), brew (pour-over platform), dual (both modes), connected (app/controller integration), dosing (gravimetric dispensing), training, bench (high capacity, coarse)
  • connectivity · string · optionnel · none | bluetooth | usb | bluetooth_usb
    How the scale talks to an app or a machine controller
  • resolution_g · number|null · optionnel
    Finest published readability in grams. Leave null unless the maker states it
  • water_resistance · string|null · optionnel
    IEC 60529 ingress code as published, e.g. IPX4, IPX6, IP67, or none
  • flow_rate_display · integer|null · optionnel
    1 if the scale shows live flow rate in g/s, 0 if it does not, null if the maker never said
  • resolution_banded · integer|null · optionnel
    1 when resolution_g only holds in the lowest weight band and coarsens with load — put the ladder in notes

  Exemple d'appel

  {"name": "register_scale", "arguments": {"name": "texte", "scale_type": "espresso"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "message": "texte", "scale_id": 1}}

• register_water≈ 328 tokens

  Register a custom or commercial water formulation.

  Paramètres, retour & exemple (9)

  Paramètres

  • gh · number|null · optionnel
    General hardness (GH) in ppm
  • kh · number|null · optionnel
    Karbonate hardness (KH) in ppm
  • tds · number|null · optionnel
    TDS in ppm
  • name · string · requis
    Water formulation name, e.g. Lotus Light & Bright, Third Wave Water
  • type · string · optionnel
    Type, e.g., mineralized, tap, distilled, RO
  • notes · string · optionnel
    Additional notes
  • sodium · number|null · optionnel
    Sodium concentration in ppm
  • calcium · number|null · optionnel
    Calcium concentration in ppm
  • magnesium · number|null · optionnel
    Magnesium concentration in ppm

  Exemple d'appel

  {"name": "register_water", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "message": "texte", "water_id": 1}}

• set_active≈ 354 tokens

  Switch the active bean, grinder or machine for this account. The numbers come from list_beans, list_grinders and list_machines. Registering a coffee, grinder or machine makes it active only when nothing of that kind is in use (the `active` field of the reply says which), so call this to start using something new as well as to switch back.

  Paramètres, retour & exemple (4)

  Paramètres

  • bean_id · integer|null · optionnel
    This account's own bean number, as returned by list_beans. Never guess one; null = leave unchanged
  • grinder_id · integer|null · optionnel
    This account's own grinder number, as returned by list_grinders. Never guess one; null = leave unchanged
  • machine_id · integer|null · optionnel
    This account's own machine number, as returned by list_machines. Never guess one; null = leave unchanged
  • program_id · integer|null · optionnel
    A program number from the active machine's list; switching machines clears it. null = leave unchanged

  Exemple d'appel

  {"name": "set_active", "arguments": {"bean_id": 1, "grinder_id": 1, "machine_id": 1, "program_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "message": "texte"}}

• set_equipment_archived≈ 208 tokens

  Archive or restore a grinder, machine, water, or scale.

  Paramètres, retour & exemple (3)

  Paramètres

  • id · integer · requis
    The ID of the equipment
  • kind · string · requis · grinder | machine | water | scale
    The kind of equipment to archive/restore
  • archived · integer · requis · 0 | 1
    1 to archive, 0 to restore

  Exemple d'appel

  {"name": "set_equipment_archived", "arguments": {"id": 1, "kind": "grinder", "archived": 0}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "message": "texte"}}

• set_grinder_position≈ 287 tokens

  Set the current grinder collar position. source="measured" resets verification freshness. It replaces the stored position; no history of earlier positions is kept.

  Paramètres, retour & exemple (3)

  Paramètres

  • source · string · requis · measured | recalled | assumed
    Whether setting is verified ("measured") or guess ("recalled"/"assumed")
  • grinder_id · integer · requis
  • setting_label · string · requis
    Verbatim display label, e.g. "1.1.2"

  Exemple d'appel

  {"name": "set_grinder_position", "arguments": {"source": "measured", "grinder_id": 1, "setting_label": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"source": "texte", "status": "texte", "message": "texte", "grinder_id": 1, "setting_label": "texte", "position_value": 1}}

• set_maintenance_offset≈ 716 tokens

  Record how far a maintenance job moved the reference, on an entry that opened a calibration epoch. Takes an ENTRY, not a piece of equipment: the offset belongs to the event that caused it, which is what lets several of them compose for a recipe locked before all of them. Zero is a legitimate measurement and means "measured, and it had not moved" — omit offset_value entirely to clear it back to unmeasured.

  Paramètres, retour & exemple (4)

  Paramètres

  • source · string · optionnel · pull | counted | typed
    How it was arrived at: pull, counted, or typed
  • entry_id · integer · requis
    The maintenance entry that opened the epoch, from list_grinders
  • evidence · string · optionnel
    One line recording what it rested on, e.g. "Reference pull 1.38 g/s against 1.74 g/s locked."
  • offset_value · number · optionnel
    Clicks to ADD to a pre-clean reading to get the same grind today, signed along the collar's own number direction. 0 records "unchanged"; omit to clear the measurement

  Exemple d'appel

  {"name": "set_maintenance_offset", "arguments": {"entry_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"entry": {}, "message": "texte"}}

• set_maintenance_schedule≈ 1198 tokens

  Set the user's own schedule for one maintenance task on one grinder or machine: their own interval, switching it off, or muting the reminder until a date. Only the keys you send in fields change; send every: null to go back to the maker's guidance and muted_until: null to unmute. Use it when the user states how often they do a task or asks to be left alone about one — never to invent an interval. The task's class, interval and due state are read back from list_grinders and list_machines.

  Paramètres, retour & exemple (5)

  Paramètres

  • task · string · requis · burr_clean | backflush_water | backflush_detergent | descale | group_gasket_replace | shower_screen_clean | shower_screen_replace | group_head_wipe
    The task, as its value in that equipment's maintenance.tasks
  • fields · object · optionnel
  • changed_at · string · optionnel
    Optional — when the user made this change (ISO 8601, UTC). An app sending a queued edit passes it, so an older edit never overwrites a newer one; it is then answered with applied: false
  • equipment_id · integer · requis
    This account's own grinder or machine number, from list_grinders or list_machines
  • equipment_kind · string · requis · grinder | machine
    Which kind of equipment the task is on

  Exemple d'appel

  {"name": "set_maintenance_schedule", "arguments": {"task": "burr_clean", "equipment_id": 1, "equipment_kind": "grinder"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"due": {}, "task": "texte", "class": "texte", "every": {}, "applied": true, "message": "texte", "schedule": {}, "equipment_id": 1, "every_source": {}, "equipment_kind": "texte"}}

• suggest_next_step≈ 157 tokens

  Retrieve the single next experiment step from the reasoning engine.

  Paramètres, retour & exemple (1)

  Paramètres

  • bean_id · integer · requis

  Exemple d'appel

  {"name": "suggest_next_step", "arguments": {"bean_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"category": "texte", "warnings": [], "next_step": "texte"}}

• update_bag≈ 697 tokens

  Change bag-level facts on one bag of a coffee: open, seal, freeze, thaw or finish it, correct its roast date, weight, grams left or price. Bag numbers come from the bags[] on list_beans (or current_bag_id). For the coffee itself — roaster, origin, roast level, rest window, notes — use update_bean.

  Paramètres, retour & exemple (3)

  Paramètres

  • bag_id · integer · requis
    This account's own bag number, from list_beans' bags[]. Never guess one.
  • fields · object · requis
  • reason · string · optionnel
    Optional free-text note, appended to this bag's notes as an ordinary line. Omit it and nothing is written.

  Exemple d'appel

  {"name": "update_bag", "arguments": {"bag_id": 1, "fields": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "message": "texte"}}

• update_bean≈ 1409 tokens

  Update a coffee's own fields (roaster, origins, roast level, rest window, notes, rating…). Bag-shaped fields sent here (state, roast_date, bag_weight_g, grams_remaining, cost…) land on the coffee's CURRENT bag — use update_bag when it has more than one. Changing dial_category changes what the engine advises (G5, C10), so say why in the optional note.

  Paramètres, retour & exemple (3)

  Paramètres

  • fields · object · requis
  • reason · string · optionnel
    Optional free-text note, appended as an ordinary line to the coffee's notes — or to the current bag's bag_notes when the call changed only bag fields. Omit it and nothing is written.
  • bean_id · integer · requis

  Exemple d'appel

  {"name": "update_bean", "arguments": {"fields": {}, "bean_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "message": "texte"}}

• update_grinder≈ 1248 tokens

  Correct a registered grinder — its name, burrs, collar scheme, nominal step, layout, range or notes. Only the keys you send in fields change; send null to clear an optional field (an empty string also clears a text field, but not a number or a closed list). Required fields can be changed but not cleared. fields may be omitted when only reason is sent. setting_scheme, nominal_step and components_spec describe the collar every recorded grind label is read through: call with dry_run first to see which recorded settings would read as a different position, and tell the user before saving. Saving records the change in the grinder's maintenance history; when a locked recipe's setting moves it also opens an unmeasured calibration epoch (set_maintenance_offset resolves it). The collar's current setting is marked assumed when it reads differently, or cleared when the new collar cannot read it, and measured offsets are converted when a click changes worth. Changing direction_convention is a correction — it moves no number, but every finer/coarser said about this grinder was the wrong way round.

  Paramètres, retour & exemple (4)

  Paramètres

  • fields · object · optionnel
  • reason · string · optionnel
    Optional note, appended to this record's own notes as an ordinary line. Omit it and nothing is written.
  • dry_run · boolean · optionnel
    true: write nothing, and answer with what the edit would do to the settings already recorded (moved[], checked, epoch, position_moved, position_cleared, rescaled_offsets, resigned_offsets, step_ignored, direction_flipped, recipe_count)
  • grinder_id · integer · requis
    This account's own grinder number, from list_grinders. Never guess one.

  Exemple d'appel

  {"name": "update_grinder", "arguments": {"grinder_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"epoch": true, "moved": [], "status": "texte", "checked": 1, "dry_run": true, "message": "texte", "entry_id": "texte", "grinder_id": 1, "unreadable": 1, "moved_count": 1, "changed_keys": [], "recipe_count": 1}}

• update_machine≈ 751 tokens

  Correct a registered machine — its name, control type, prep type and style, basket, boiler, accessories or notes — or record where its selectors stand (settings). Only the keys you send in fields change; send null to clear an optional field (an empty string also clears a text field, but not a number or a closed list). Required fields can be changed but not cleared. fields may be omitted when only reason is sent. prep_style decides whether shots on this machine are diagnosed at all: only "espresso" is. Programs are edited with register_program, the built-in grinder link is not editable here, and archiving is set_equipment_archived.

  Paramètres, retour & exemple (3)

  Paramètres

  • fields · object · optionnel
  • reason · string · optionnel
    Optional note, appended to this record's own notes as an ordinary line. Omit it and nothing is written.
  • machine_id · integer · requis
    This account's own machine number, from list_machines. Never guess one.

  Exemple d'appel

  {"name": "update_machine", "arguments": {"machine_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "message": "texte", "machine_id": 1, "changed_keys": []}}

• update_scale≈ 568 tokens

  Correct a registered scale — its type, resolution, capacity, capabilities, build or notes. Only the keys you send in fields change; send null to clear an optional field (an empty string also clears a text field, but not a number or a closed list). Required fields can be changed but not cleared. fields may be omitted when only reason is sent. The three capabilities are 1, 0, or null for "the maker never said"; leave one out rather than sending 0 when nobody knows.

  Paramètres, retour & exemple (3)

  Paramètres

  • fields · object · optionnel
  • reason · string · optionnel
    Optional note, appended to this record's own notes as an ordinary line. Omit it and nothing is written.
  • scale_id · integer · requis
    This account's own scale number, from list_scales. Never guess one.

  Exemple d'appel

  {"name": "update_scale", "arguments": {"scale_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "message": "texte", "scale_id": 1, "changed_keys": []}}

• update_shot≈ 850 tokens

  Correct fields on an already-logged shot in place — no need to delete and re-log. Use for fixing a wrong dose/yield/time or grind label, re-filing a shot onto the right bean (bean_id), backfilling rating/tasting notes, or fixing the timestamp (pulled_at). Changing grind_label re-derives the numeric grind position from the shot's grinder; changing yield/time/dose/tds keeps flow rate and extraction yield consistent automatically.

  Paramètres, retour & exemple (2)

  Paramètres

  • fields · object · requis
    Only the fields to change
  • shot_id · integer · requis
    ID of the shot to correct

  Exemple d'appel

  {"name": "update_shot", "arguments": {"fields": {}, "shot_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "message": "texte", "shot_id": 1, "updated_fields": []}}

• update_water≈ 387 tokens

  Correct a registered water — its name, type, mineral figures or notes. Only the keys you send in fields change; send null to clear an optional field (an empty string also clears a text field, but not a number or a closed list). Required fields can be changed but not cleared. fields may be omitted when only reason is sent.

  Paramètres, retour & exemple (3)

  Paramètres

  • fields · object · optionnel
  • reason · string · optionnel
    Optional note, appended to this record's own notes as an ordinary line. Omit it and nothing is written.
  • water_id · integer · requis
    This account's own water number, from list_waters. Never guess one.

  Exemple d'appel

  {"name": "update_water", "arguments": {"water_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "message": "texte", "water_id": 1, "changed_keys": []}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.shotpulled.com/mcp