Skip to main content
Glama
chrischall

artsonia-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Set notification preferences

artsonia_set_notifications

Enable or disable Artsonia email opt-ins for news, artist activity, and promos without changing your name, email, or password. Changes apply immediately and are re-read to verify.

Instructions

Turn the account's email opt-ins on/off (news, artist activity, promos). Reads your profile, changes only the opt-in(s) you specify, and re-saves — leaving your name/email/password untouched. Runs immediately, with no confirmation step, then re-reads the profile to verify the change stuck.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
newsNoOptInNews — general Artsonia news emails.
promosNoOptInPromos — promotional/keepsake emails.
artist_activityNoOptInArtistActivity — emails about your student(s) activity.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.1
    • removedInput schema / properties / confirmToken
      Removed value: -{
-  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
-  "type": "string"
-}
  2. First observedv1.2.1

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), it discloses the full read-modify-write pattern, guarantees that name/email/password are left untouched, warns there is no confirmation step, and states it re-reads the profile to verify the change persisted. Those are exactly the behaviors an agent needs before firing a mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each carrying distinct payload: the action, the partial-update/safety contract, then the execution and verification behavior. The purpose is front-loaded and there is no filler.

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 low-complexity three-flag mutation with no output schema, the description covers the side-effect profile, the partial-update contract, and the post-write verification. It omits what happens if no opt-in is supplied at all (no-op vs error) and any auth prerequisite, which are minor but real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a baseline of 3 applies, but the description adds the crucial semantics the schema omits: all three booleans are optional and omitted ones are left unchanged rather than reset to false. It also restates the category mapping (news, artist activity, promos), confirming which flag each parameter drives.

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 and resource ('Turn the account's email opt-ins on/off') and enumerates the three opt-in categories, which map cleanly to the schema properties. An agent can distinguish this from read-side siblings like artsonia_get_profile without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the usage context explicit: it is a partial update ('changes only the opt-in(s) you specify') that applies immediately with no confirmation step, so an agent knows this is the mutation path for notification settings. It stops short of naming when-not-to-use conditions or pointing to any alternative, but there is no close sibling to disambiguate against.

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

Deploy Server

Other Tools