Skip to main content
Glama

Dismiss Action Center Item

dismiss_action_center_item

Dismiss one action center item for a managed community. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>",
      "actionCenterObjectId": "<actionCenterObjectId>",
      "key": "<key>"
    },
    "name": "dismiss_action_center_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesAction center item key, from the CMP home action center.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
actionCenterObjectIdYesAction center item object ID, from the CMP home action center.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / actionCenterObjectId / description
      Added value: +"Action center item object ID, from the CMP home action center."
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / key / description
      Added value: +"Action center item key, from the CMP home action center."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this as a non-read-only, non-destructive, closed-world mutation, and the description adds real policy context beyond that: the FREE-tier exclusion, the mandatory access check step, and grace-period/resubscribe messaging requirements. It does not say whether a dismissal is reversible or how the item's state changes afterward, which is the main remaining behavioral gap.

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?

Purpose is front-loaded in the first sentence, followed by access gates in a logical pre-call order. There is minor redundancy between 'check business permissions' and 'Call check_business_tool_access,' but no sentence is wasted for a tool with real authorization constraints.

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 three-parameter mutation with no output schema, the description covers the critical gating behavior an agent must respect before calling. It omits the post-dismissal effect (whether the item can reappear or be restored), which is a modest but real gap for a state-changing tool.

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 description coverage is 100% with all three required parameters documented inline, including the warning not to invent a communityId. The description adds no format, syntax, or sourcing detail beyond what the schema already supplies, so the baseline of 3 applies.

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 plus resource and scope: 'Dismiss one action center item for a managed community.' The singular 'one item' scope cleanly separates it from the sibling retrieval/completion tools such as get_action_center and complete_cmp_home_get_started_item.

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?

Gives a clear precondition flow: call check_business_tool_access before collecting inputs, never proceed when access is blocked, and show grace-period messaging first. It stops short of naming an alternative path for discovering or listing items to dismiss, leaving that to the schema's 'from the CMP home action center' hint.

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