Skip to main content
Glama

get_reliability_rules

Read-only

Retrieve active prevention rules and success patterns to enhance system reliability and prevent failures in memory management.

Instructions

Retrieve active prevention rules and success patterns. Aliased to prevention_rules.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for 'prevention_rules' (aliased from 'get_reliability_rules') which calls 'writePreventionRules'.
    case 'prevention_rules': {
      const outputPath = args.outputPath ? resolveSafePath(args.outputPath) : undefined;
      return toTextResult(writePreventionRules(outputPath, Number(args.minOccurrences || 2)));
    }
  • The implementation of 'writePreventionRules' which generates the markdown and registers it with the context system.
    function writePreventionRules(filePath, minOccurrences = 2) {
      const { PREVENTION_RULES_PATH } = getFeedbackPaths();
      const outPath = filePath || PREVENTION_RULES_PATH;
      const markdown = buildPreventionRules(minOccurrences);
      ensureDir(path.dirname(outPath));
      fs.writeFileSync(outPath, `${markdown}\n`);
    
      const contextFs = getContextFsModule();
      if (contextFs && typeof contextFs.registerPreventionRules === 'function') {
        try {
          contextFs.registerPreventionRules(markdown, { minOccurrences, outputPath: outPath });
        } catch {
          // Non-critical
        }
      }
      return { path: outPath, markdown };
    }
  • Definition and registration of the 'get_reliability_rules' tool.
    readOnlyTool({
      name: 'get_reliability_rules',
      description: 'Retrieve active prevention rules and success patterns. Aliased to prevention_rules.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    }),
Behavior3/5

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

Annotations indicate readOnlyHint=true, which the description aligns with by using 'retrieve' (a read operation). The description adds minimal context by specifying 'active' rules and patterns, but does not disclose further behavioral traits like rate limits, authentication needs, or response format, leaving gaps despite the annotation.

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?

The description is brief and front-loaded, stating the core purpose in the first clause. The second clause about aliasing is relevant but could be integrated more smoothly. Overall, it avoids unnecessary verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters, annotations cover read-only behavior, and no output schema exists, the description is minimally adequate. However, it lacks details on what 'active' means, how results are structured, or error handling, leaving room for improvement in guiding an agent.

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?

With 0 parameters and 100% schema description coverage, the input schema fully documents the lack of parameters. The description does not add parameter-specific information, which is unnecessary here, so it meets the baseline for tools with no parameters.

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

Purpose3/5

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

The description states the tool 'retrieve[s] active prevention rules and success patterns', which provides a clear verb ('retrieve') and resource ('prevention rules and success patterns'). However, it does not distinguish this tool from its sibling 'prevention_rules' beyond noting they are aliased, leaving ambiguity about their functional differences.

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

Usage Guidelines2/5

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

The description offers no guidance on when to use this tool versus alternatives. It mentions an alias to 'prevention_rules' but does not explain when one should be preferred over the other or provide any context for usage, such as prerequisites or typical scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IgorGanapolsky/mcp-memory-gateway'

If you have feedback or need assistance with the MCP directory API, please join our Discord server