Skip to main content
Glama

Read the gated sensitive store (legal/medical)

memory_sensitive_get

Retrieve sensitive records (medical, legal) from a gated store when not in normal context; filter by topic or list all.

Instructions

Retrieve sensitive records (e.g. legal, medical) from the gated sensitive store. These records are NOT in your normal context — they are never auto-loaded and never searched — so you MUST call this tool when the user asks about, or you need, sensitive info like medications, legal status, etc. Optional topic filters by record name (e.g. 'medical', 'legal'); omit to list all. This read is gated only when the turn contains untrusted content (then it requires approval); a normal request from the owner runs directly. Never copy sensitive content into durable memory (memory_promote) or any outbound/external action.

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": "memory_sensitive_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoOptional record-name filter (e.g. 'medical', 'legal'); omit to return all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses the gating condition (approval required only when the turn contains untrusted content, direct execution otherwise), which is exactly the kind of permission/approval nuance an agent cannot infer. It also discloses the data-placement behavior (never auto-loaded, never searched) and a safety constraint on downstream use.

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?

Front-loaded with purpose and criticality, then parameter detail, then the gating rule — a sensible ordering with almost no wasted words. The closing prohibition against copying into memory_promote or outbound actions is slightly tangential but earns its place as a guardrail.

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 one-optional-parameter read tool with no output schema, the description covers retrieval, filtering, gating, and safe downstream handling. The only gap is that it never hints at the shape or volume of returned records, which an agent cannot get from a nonexistent output schema.

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%, so the single `topic` parameter is already documented, and the description largely restates it (record-name filter, examples 'medical'/'legal', omit to list all). It adds no new syntax, matching behavior, or format detail beyond the schema, so baseline 3 is correct.

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 and resource ("Retrieve sensitive records... from the gated sensitive store") and immediately distinguishes this store from normal context by noting these records are never auto-loaded and never searched. That scope statement makes clear this is the only path to this data, which no sibling tool name alone would convey.

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?

Explicitly says when to call ("you MUST call this tool when the user asks about, or you need, sensitive info like medications, legal status") and gives concrete trigger examples. It also names the counter-action to avoid, redirecting away from memory_promote for durable copying, which is the main misuse risk for this data.

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