Skip to main content
Glama
eonik-ai

eonik-mcp

Official

remember

Store durable brand insights from marketer conversations as structured subject-relation-object facts, automatically superseding outdated entries for future reference.

Instructions

Record something durable about THIS brand that you learned from the marketer — a decision, a correction, a rejection, an outcome. State it as a relation you already understand: subject + relation + object, plus the fact in one sentence and the marketer's own words if they said it. Recording 'the hook is X' when 'the hook is Y' was recorded before automatically supersedes the old fact (it becomes history, not a contradiction). Use it when the marketer tells you something that should still be true next session; do NOT use it for chit-chat or for anything already in the brand context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
factYesThe whole thing in one plain sentence — this is what you will read back later.
quoteNoThe marketer's own words, verbatim, if they said it.
objectNoThe other end of the relation, e.g. 'discount-led openings'.
subjectYesWhat the fact is about, e.g. 'Comeek' or 'the revenge-arc hook'.
relationYesThe verb, lowercase and stable, e.g. 'rejected', 'prefers', 'stopped_using', 'decided'.
artifact_refNoThe id of the ad / project / slate this attaches to, so the fact keeps a receipt.
object_labelNo
artifact_kindNoWhat that id refers to, e.g. 'watch_asset', 'project', 'slate'.
subject_labelNo
Behavior5/5

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

The description discloses the supersede behavior: recording the same relation with a different fact automatically replaces the old fact, turning it into history. This is a critical behavioral trait not apparent from the schema. With no annotations provided, the description fully carries the burden of explaining side effects and persistence semantics.

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 paragraph but well-structured with clear guidance on format, usage, and exclusion. Every sentence adds value: purpose, evidence format, supersede behavior, and usage boundaries. It is appropriately concise for the complexity of the tool.

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 tool has 9 parameters but the description provides enough context to understand the required inputs (subject, relation, fact) and the optional ones (quote, object, artifact_ref). It explains the return behavior implicitly (the fact will be read back later). With no output schema, the description adequately covers the essential context for invocation.

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?

The schema covers 78% of parameters with descriptions, but the description adds critical semantics: the fact field is 'what you will read back later', quote is 'marketer's own words', and the relation format is 'lowercase and stable'. The description also explains the subject+relation+object structure, which adds meaning beyond the schema's individual field descriptions.

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's purpose: to record durable facts about the brand learned from the marketer. It specifies the verb ('record'), the resource ('something durable about THIS brand'), and differentiates from siblings by emphasizing persistence and the supersede behavior. It also gives concrete relation format examples.

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?

The description explicitly states when to use it ('when the marketer tells you something that should still be true next session') and when not to use it ('do NOT use it for chit-chat or for anything already in the brand context'). This clear usage context helps the agent decide between this and other saving tools like save_context_note or save_brand_truth.

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

Install Server

Other Tools

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/eonik-ai/eonik-mcp'

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