Skip to main content
Glama

dismiss_client_onboarding

Destructive

Close a client's onboarding checklist without finishing it (confirm-gated) — it stops showing up and stops nudging.

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": "dismiss_client_onboarding"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
clientIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds real behavioral value beyond that: the action is confirm-gated and its effect is that the checklist stops appearing and stops sending reminders. It does not say whether a dismissal can be undone, which is the remaining gap.

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?

One sentence, front-loaded with the action, then the qualifier, then the observable effect. No filler and nothing redundant.

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 destructive, confirm-gated mutation with no output schema, the description covers what the action does and its visible consequences. The only meaningful omission is reversibility — whether a dismissed checklist can be restored — and how progress data is retained.

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 50%: confirm is fully documented in the schema (including preview-only behavior when false), while clientId has no description. The description's '(confirm-gated)' reinforces the confirm parameter but adds nothing about clientId, so it neither compensates nor detracts much.

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?

States a specific verb and resource (close a client's onboarding checklist) with the key qualifier 'without finishing it', which separates it from the step-completion siblings like mark_client_onboarding_step. It does not name an alternative explicitly, so it falls short of the top mark.

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?

The phrase 'without finishing it' implies the choice between completing and abandoning onboarding, and 'stops showing up and stops nudging' hints at intent. There is no explicit when-to-use/when-not-to-use rule or named alternative (e.g. mark_step vs dismiss).

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.