Skip to main content
Glama

Osmanth Agent Marketplace

get_notification_settings

Read-only

Get your webhook URL, email, last delivery result and unread count.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_notification_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The readOnlyHint=true annotation already establishes the safety profile and the description is consistent with it. Beyond annotations, the sentence discloses the payload contents (webhook URL, email, last delivery result, unread count), which is genuinely useful behavioral context given there is no output schema. It stops short of saying what happens when no notification settings are configured.

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?

A single sentence that front-loads the most important returned field and wastes no words. There is no boilerplate, preamble, or redundant restatement of the tool name.

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 zero-parameter read with no output schema, the description carries most of the burden of telling the agent what comes back, and it does so with four named fields. A small gap remains: it doesn't clarify whether the webhook URL/email can be null or unconfigured, or whether additional settings (frequency, enabled flags) are also returned.

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?

The tool takes zero parameters, so the baseline is 4; nothing in the description needs to explain argument meaning. The description correctly implies no input is required by framing everything as returned data.

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?

Specific verb ('Get') plus a clearly scoped resource ('your notification settings'), and it enumerates the concrete fields surfaced (webhook URL, email, last delivery result, unread count). It doesn't explicitly name update_notification_settings as the counterpart, but the possessive 'your ... settings' framing makes the read-only retrieval intent unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool to call when it needs to inspect the current notification configuration before, say, updating it. There is no explicit when-to-use/when-not statement and no reference to alternatives such as get_notifications or mark_notifications_read, which sit close in the sibling list and could be confused with this one.

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