Skip to main content
Glama
Sign In

OwlMem

by com.owlmem
OverviewDiscussionsAdmin

vault_deny

Deny a pending vault request for your person, only when they ask you to. Only their notice assistant can use it, and only for requests they could approve. AI agents can't approve. Your person gets a notification, and the audit log shows you denied it on their behalf.

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": {
      "request_id": "<request_id>"
    },
    "name": "vault_deny"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional: why (kept in the vault audit log, up to 200 characters)
request_idYesThe request_id from kb_notices

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark this as a non-read-only, non-destructive mutation. The description adds meaningful behavior beyond that: the person receives a notification, the denial is attributed in the audit log, and use is restricted to the notice assistant.

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 core action and constraints are front-loaded in the first sentence. The remaining sentences add authorization, side-effect, and audit context without unnecessary repetition.

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?

The description covers authorization, eligibility, and side effects for a mutation tool with no output schema. It does not describe what the tool returns on success or failure, but otherwise gives an agent enough context to call it correctly.

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 100%, and both parameters already have descriptions, including that request_id comes from kb_notices. The description adds no additional syntax or format detail for request_id or note, so the baseline of 3 is appropriate.

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: denying a pending vault request for the user's person. It also scopes the action to requests the person could approve and identifies the authorized actor, so an agent can distinguish this from unrelated kb_* tools.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance: only when the person asks, only by their notice assistant, and only for requests they could approve. It also states the exclusion that AI agents cannot approve, leaving little ambiguity.

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