SoluCortex

solucortex_remember

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

Name	Required	Description
`type`	Yes	Memory 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.
`title`	Yes	Short, clear title (~80 chars max).
`content`	Yes	Full content: what to remember, why it matters, where it applies and what it prevents. NEVER include real secrets (tokens, passwords, .env, credentials).
`importance`	No	Priority 1-10. Default 5. 6-7 high; 8-9 important decision/risk/convention; 10 critical.
`project_id`	No	Project UUID. If omitted, the session default applies, else the backend infers it from the API key.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Description adds that memories are 'stored with status 'approved' and traced' and includes a security policy for secrets, which is beyond the annotations (readOnlyHint false, destructiveHint false).

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?

Two concise sentences: first states the action, second provides use cases and security guidance, with no fluff.

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?

For a simple create-like tool, it covers purpose, usage timing, authentication, and secret redaction; the sibling list provides context without needing more detail.

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 descriptions cover all parameters with meaning, ranges, defaults, and examples like canonical vocabulary for type and max length for title, so the description adds minimal extra but is reinforced by the thorough schema.

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?

Clearly states 'Record a memory in SoluCortex (POST /memories)' with a specific verb and resource, and distinguishes from siblings like list, recall, search, update, and flag.

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?

Explicitly says 'Call when closing a task or making a relevant technical decision' and mentions authorization via Bearer api_key, though it doesn't explicitly contrast with alternatives.

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

All SoluCortex tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.