Skip to main content
Glama

project_notice_acknowledge

Idempotent

Mark a somewhere platform notice read or snooze its reminders for this maintainer. This only changes personal notice delivery; it never resolves the underlying project issue or grants any capability.

It takes the project_id and notice_id supplied with the notice. A snooze defaults to 24 hours and accepts 1–720 whole hours.

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>",
      "notice_id": "<notice_id>",
      "action": "<action>"
    },
    "name": "project_notice_acknowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesMark read permanently for this maintainer, or temporarily snooze reminders.
notice_idYesNotice identifier supplied in the notice delivery context.
project_idYesProject UUID, subdomain, or slug supplied with the notice.
snooze_hoursNoWhole hours from 1 to 720. Used only with action "snooze"; defaults to 24.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations give readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is already covered. The description goes beyond that by explicitly limiting the scope of the write to personal notice delivery and by spelling out the snooze default and 1–720 whole-hour range, which a caller needs to know before choosing 'snooze'.

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 clause, followed by the scope caveat, with zero filler. The second paragraph partly restates schema facts (24-hour default, 1–720 hours), which is mild redundancy but keeps the definition short overall.

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 four-parameter, non-destructive, idempotent state-change tool with full schema coverage and no output schema, the description covers the one thing structured fields cannot: that acknowledging a notice has no effect on the underlying project issue. Nothing critical to correct invocation is missing.

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%, so all four parameters, including the action enum and snooze_hours bounds, are already documented in structured data. The description repeats the snooze default and range and notes that project_id/notice_id come with the notice, but adds no syntax or format meaning beyond the schema — baseline 3.

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 pair and resource: 'Mark a somewhere platform notice read or snooze its reminders'. It also bounds the effect ('only changes personal notice delivery') which separates it from the project-level mutation siblings like project_archive or project_patch, so an agent can tell what this is not.

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?

Clear context for use — mark read or snooze reminder delivery for this maintainer, with ids supplied with the notice. It adds useful negative guidance ('never resolves the underlying project issue or grants any capability'), which is exactly the misconception an agent might have, but it does not name any alternative action to take instead when the intent is to resolve an issue.

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