Skip to main content
Glama

get_client_notification_settings

Read-only

A client's reminder settings (email/push and quiet hours) — e.g. to see why they aren't getting check-in reminders.

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": {
      "clientId": "<clientId>"
    },
    "name": "get_client_notification_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientIdYesClient's User _id (from list_clients)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is established. The description adds scope detail — that email/push and quiet hours are the settings returned — but says nothing about defaults, inheritance from global settings, or what an empty/partial result means.

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 front-loaded clause identifying the resource and its contents, followed by a parenthetical use case. No filler, no redundancy.

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 one-parameter read tool with full schema coverage, annotations, and no output schema, the description says enough to call it correctly and understand the payload's scope. Only minor detail (e.g. behavior when settings are unset) is absent.

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 100% and the single clientId parameter is already documented in the schema with a pointer to list_clients. The description adds no further parameter meaning, so the baseline 3 applies.

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 description names the resource (a client's reminder settings) and enumerates the content it covers (email/push channels, quiet hours), which distinguishes it from the general notification-count and my-settings siblings. It does not use an explicit verb, relying on the title's 'Get', but the resource scope is 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?

A concrete motivating scenario is given ('to see why they aren't getting check-in reminders'), which implies this is a diagnostic read. It does not explicitly say when to use update_client_notification_settings instead, nor state prerequisites beyond the implied clientId requirement.

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.