Skip to main content
Glama
MemoryShield+ Agent Plugin

MemoryShield+ Agent Plugin

by GFDDFDGHJ

memoryshield_status

Read-onlyIdempotent

Checks backend health and configured model names without model requests, so agents can verify MemoryShield+ configuration presence.

Instructions

Read backend health and configured model names with zero model calls.

Health checks configuration presence. Provider billing and write success require actual model requests and are outside this configuration check.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds real value by clarifying that the check makes zero model calls and therefore proves nothing about billing or write success, which prevents the agent from over-trusting a 'healthy' result.

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-loads the core action and the 'zero model calls' qualifier in the first sentence, with the caveats following. The second and third sentences overlap somewhat ('Health checks configuration presence' vs. 'outside this configuration check'), a minor redundancy rather than padding.

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?

With an output schema present and no inputs, the description need not explain return values, and it covers scope and limits well. What 'backend health' concretely enumerates beyond configuration presence remains slightly generic, keeping it below a 5.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. There is nothing parameter-level for the description to explain, and it correctly avoids inventing input semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Read backend health and configured model names,' plus the distinguishing constraint 'with zero model calls.' This lets an agent separate it from the data-oriented siblings memoryshield_recall and memoryshield_remember, though it never names those siblings explicitly.

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?

Gives clear context for when the tool applies ('Health checks configuration presence') and an implicit when-not: it cannot verify provider billing or write success because those need real model requests. No alternatives are named, but the scope boundary is explicit rather than inferred.

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