Skip to main content
Glama
Sign In
Txa_MCP

Txa_MCP

by TXAVLOG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

memory_save

Persist important knowledge and decisions in project memory. Use key-value pairs to store details in .txamcp_memory for later retrieval.

Instructions

Store important knowledge/decisions in project memory (.txamcp_memory).

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": {
      "key": "<key>",
      "value": "<value>"
    },
    "name": "memory_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesIdentifier key
valueYesContent to remember

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.3

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It only says 'store' without disclosing whether saving overwrites existing keys, how conflicts are handled, or what the return behavior is. The mention of the .txamcp_memory file adds location context but not enough behavioral transparency for a write operation.

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 description is a single sentence that is direct and front-loaded with the verb and object. Every word earns its place, with no filler or repetition.

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?

The tool is simple with only two params, both well-documented in the schema. However, the lack of annotations and any behavioral detail (e.g., upsert semantics, return value) leaves the description minimally adequate but not comprehensive. Given the simple nature, a 3 is fair.

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?

The input schema provides complete descriptions for both parameters ('Identifier key' and 'Content to remember'), covering 100% of the schema. The description adds no extra semantic detail beyond the schema, so the baseline of 3 applies.

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?

The description clearly states the action ('Store') and the resource ('important knowledge/decisions in project memory'), and specifies the local file (.txamcp_memory), which differentiates it from the sibling cloud_memory_save. However, it does not explicitly name the alternative, so it falls short of a perfect 5.

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 implies usage for project-local memory but gives no explicit when-to-use or when-not-to-use guidance, nor does it reference the cloud_memory_save sibling. The context is clear but non-exclusive, so a 3 is appropriate.

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