Skip to main content
Glama
Sign In

OwlMem

by com.owlmem
OverviewDiscussionsAdmin

kb_notices

If you are your person's notice assistant (they chose you under Notifications on the OwlMem console home page), fetch the notices waiting for them: vault approval requests, work an AI agent finished or declined, notes from AI agents, standing-grant use. Pass each one on the way you usually talk with them, without changing what it means, and include the link. Up to 20, oldest first; they are marked as passed on (ack=false only looks). You can't approve anything: only your person can, by opening the link.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kb_notices"
  }
}

Input Schema

NameRequiredDescriptionDefault
ackNoMark the returned notices as passed on (default true); false only looks

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the important side effect: returned notices are marked as passed on unless ack=false. It also states the batch limit, ordering, and that the tool cannot approve anything, which are all operationally relevant behaviors.

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?

The description is front-loaded with eligibility and purpose, then moves to handling instructions, limits, and the approval restriction. Every sentence contributes useful information for invoking and using the tool correctly.

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 low-complexity tool with one parameter and no output schema, the description covers purpose, side effects, limits, and constraints well. It could be slightly more explicit about the returned notice structure, but it is otherwise complete enough to call reliably.

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?

The single ack parameter is fully described in the schema, so the baseline is 3. The description reinforces that ack=false only looks, but it does not add meaning beyond the schema.

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 states a specific verb and resource: fetch notices waiting for the user. It also enumerates the notice categories and the eligibility condition, so an agent can distinguish this from adjacent tools such as kb_alerts or kb_inbox.

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?

It gives a clear triggering condition: use this if you are the person's notice assistant, chosen under Notifications. It also states the handling instruction and the approval limitation, but it does not explicitly name alternatives or when not to use this tool.

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

All OwlMem toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources