Skip to main content
Glama
soluai-spa

solucortex-mcp

Official
by soluai-spa

solucortex_remember

Closing a task or making a technical decision? Record an approved, traced memory in SoluCortex to preserve project context and prevent future mistakes.

Instructions

Record a memory in SoluCortex (POST /memories).

Call when closing a task or making a relevant technical decision. As an authorized agent (Bearer api_key), the memory is stored with status 'approved' and traced. Never store real secrets: if you find one, record location/type/severity and action taken, with a redacted reference.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesMemory type. The backend validates the value. Canonical vocabulary: architecture, decision, risk, convention, bug_history, tech_debt, sensitive_module, learning, external_integration. (Older backends may use technical_decision, historical_bug, current_state, task_closure.) On HTTP 422, retry with the alternate vocabulary.
titleYesShort, clear title (~80 chars max).
contentYesFull content: what to remember, why it matters, where it applies and what it prevents. NEVER include real secrets (tokens, passwords, .env, credentials).
importanceNoPriority 1-10. Default 5. 6-7 high; 8-9 important decision/risk/convention; 10 critical.
project_idNoProject UUID. If omitted, the session default applies, else the backend infers it from the API key.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.0.0
    • changedInput schema / properties / project_id / description
      Previous value: -"Project UUID. If omitted, uses SOLUCORTEX_PROJECT_ID."New value: +"Project UUID. If omitted, the session default applies, else the backend infers it from the API key."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Given annotations already indicate this is a non-read, non-destructive, non-idempotent operation, the description adds valuable behavioral context: the memory is stored with status 'approved' and is traced, and a bearer API key is required. It also discloses the safe-handling policy for secrets, which goes beyond the structured annotations.

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 four concise sentences with no filler. The core action is front-loaded, followed by when-to-use, behavioral context, and the security caveat. Every sentence earns its place.

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

Completeness5/5

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

The description is complete for a memory-creation tool: it covers action, trigger conditions, authentication, post-condition (approved/traced), and secret-handling policy. With an output schema present and comprehensive parameter schemas, nothing essential is missing.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds meaning by explaining how to handle sensitive content in the `content` parameter: record location/type/severity and action taken with a redacted reference. This is practical guidance beyond the schema's 'NEVER include real secrets' note.

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 opens with a specific verb and resource: 'Record a memory in SoluCortex (POST /memories)'. It clearly distinguishes this write operation from its siblings (list, recall, search) by naming the creation endpoint and memory domain.

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?

The description explicitly states when to call the tool: 'Call when closing a task or making a relevant technical decision.' It does not mention exclusions or alternatives, but the sibling tools are clearly different operations, so the primary usage context is sufficient.

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

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/soluai-spa/solucortex-mcp'

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