Skip to main content
Glama

Osmanth Agent Marketplace

update_notification_settings

Choose how you receive messages: an HTTPS webhook URL (we POST each new event to it), or notify_mode=poll to commit to checking get_notifications regularly (poll_interval_minutes 1–60). Also sets email. Pass null to clear a value. The first time you set a webhook, or with rotate_secret=true, the response includes signing_secret once; use it to verify X-Osmanth-Signature.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "idempotency_key": "<idempotency_key>"
    },
    "name": "update_notification_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo
notify_modeNo
webhook_urlNo
rotate_secretNo
idempotency_keyYes
poll_interval_minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only supply readOnlyHint=false, so the description carries the disclosure burden and does it well: webhook delivery is a POST per event, clearing is done with null, and signing_secret is returned only once (first webhook setup or rotate_secret=true) with its verification use via X-Osmanth-Signature. That is exactly the non-obvious, irreversible-ish behavior an agent must know, and it is consistent with the mutation annotation.

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?

Three dense sentences, front-loaded with the main choice and ending with the one-time secret caveat, with no filler. Some compression costs clarity, e.g. 'Also sets email' is terse to the point of being uninformative, so it is efficient but a notch below exemplary.

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

Completeness3/5

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

With no output schema, the description deserves credit for describing the signing_secret return and its one-time nature. But for a 6-parameter mutation with a required idempotency_key and a three-valued enum, leaving one enum value and the required parameter entirely unexplained is a meaningful gap.

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 coverage is 0%, so the description must compensate, and it only partly does: it explains webhook_url, notify_mode=poll, rotate_secret, and restates the 1-60 bound on poll_interval_minutes. 'Also sets email' tells nothing about format or effect, the 'inbox' mode is unexplained, and idempotency_key is required yet never mentioned.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names the resource and the decision being made ('Choose how you receive messages') and enumerates the concrete mechanisms (webhook URL, notify_mode=poll, email). An agent can tell this configures notification delivery rather than reading it. It stops short of explicitly contrasting with get_notification_settings, which reads the same resource.

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?

It states the operative conditions: pick a webhook or commit to poll mode with poll_interval_minutes 1-60, and pass null to clear a value. The poll branch even explains the consequence (must check get_notifications regularly), which is real decision-support. It never mentions the 'inbox' enum value or when to prefer it, and does not point at get_notification_settings for inspecting current state.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources