Skip to main content
Glama

AiAkiv Memory

by com.aiakiv
OverviewDiscussionsAdmin

describe_memory_schema

Read-onlyIdempotent

Return the memory database's tables, columns, and types.

Use this when a SQL query needs the schema first. Do not use it to read
stored content; it describes structure alone.

Read-only and cheap. The schema itself is public information; the data in
those tables stays protected by RLS.

Returns:
    Every table with its columns and their types.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint, idempotentHint, and not destructive. The description adds useful context: it is 'cheap' and mentions RLS protection, which adds behavioral nuance beyond annotations. No contradiction.

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 compact, with key purpose and usage in the first two sentences, and additional behavioral context in the third. Every sentence adds value; 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?

Given no parameters and an output schema (implicitly mentioned by the 'Returns' section), the description fully covers what an agent needs: purpose, usage guidance, behavioral traits, and return value summary. Nothing 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?

There are no parameters, so the schema is trivial. The description doesn't need to explain parameters; it correctly focuses on the tool's output and usage, which is sufficient. Baseline for 0 params is 4.

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 clearly states the tool returns schema (tables, columns, types), which is specific and distinguishes it from sibling tools focused on content retrieval or manipulation. It uses a specific verb 'Return' and resource 'memory database's tables, columns, and types', making it unambiguous.

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

Usage Guidelines5/5

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

It explicitly states when to use ('when a SQL query needs the schema first') and when not to use ('Do not use it to read stored content'), and distinguishes from alternatives by stating it 'describes structure alone'.

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

All AiAkiv Memory toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources