Skip to main content
Glama
Sign In
agent-nexus

agent-nexus

by dugubuyan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ack_update

Acknowledge a notification by marking it as read. Provide the project and update IDs to confirm receipt of the update.

Instructions

Acknowledge (mark as read) a notification.

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": {
      "project_id": "<project_id>",
      "update_id": "<update_id>"
    },
    "name": "ack_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
update_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only states the action but doesn't disclose side effects, idempotency, or required permissions. The agent cannot infer behavioral traits beyond the simple verb.

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?

The description is a single, front-loaded sentence with no filler. However, it is arguably too sparse, sacrificing informative content for brevity.

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

Completeness2/5

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

Given the tool's simplicity, the description lacks completeness. It does not explain the effect of acknowledgment, return behavior (void?), or how to obtain valid parameter values. Agent is left with significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain the parameters project_id and update_id. Parameter names provide some hints, but the description adds no value beyond the schema. The agent relies on guessing or external knowledge.

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?

The description clearly states the verb 'acknowledge' and the resource 'notification', with parenthetical 'mark as read' for clarity. It is specific and distinct from sibling tools like get_my_updates, which list notifications.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, such as needing a valid project_id or update_id, or context like what happens after acknowledging.

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

Deploy Server

Other Tools