Skip to main content
Glama
Sign In
GitMem

GitMem

Official
by gitmem-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gitmem-cache-flush

Force reload cache from Supabase to resolve out-of-sync issues between AI sessions and stored memory.

Instructions

gitmem-cache-flush - Force reload cache from Supabase (use when out of sync)

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": "gitmem-cache-flush"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNoProject namespace (e.g., 'my-project'). Scopes sessions and searches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.4

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It states the action (force reload) but does not explain side effects, permission requirements, or what 'out of sync' means operationally. For a cache flush, this lack of detail is a significant gap.

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 extremely concise—one sentence—and front-loaded with the tool name and purpose. Every word is functional, but the brevity sacrifices necessary details.

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

Completeness2/5

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

For a simple one-parameter tool with no output schema and no annotations, the description should still explain what 'out of sync' means, what happens to the cache, and whether the operation is reversible. It lacks this context, so completeness is low.

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% for the single parameter 'project', and the schema description is clear. The tool description adds no additional meaning beyond the schema, meeting the baseline of 3.

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 explicitly states 'Force reload cache from Supabase', which is a specific verb and resource. It clearly distinguishes from sibling tools like gitmem-cache-health and gitmem-cache-status by focusing on flushing the cache.

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

Usage Guidelines3/5

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

The description includes 'use when out of sync', providing a clear context for when to use the tool. However, it does not specify when not to use it, nor does it mention alternatives among sibling tools.

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

Deploy Server

Other Tools