Emero

Get emero brain

get_emero_brain

Read-onlyIdempotent

Read this brand's emero brain in full: the look-lock sheet, style and model leanings, defaults, graded rules (require/forbid/prefer), locked subjects (Characters/Products, each with an anchor id to pass as reference_image_ids) and decisions — brand-wide plus this project's, each with its id, and the brand's other projects. Call it before the first generation for a brand: generations reuse its anchors and look-lock to stay consistent, and it is the same brain across every chat, device and teammate. get_settings shows a short version. Empty = no brain yet; it grows with save_to_emero_brain. load_skill("emero-brain") for the shape.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_emero_brain"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	No	Opaque per-chat project id: "p-" plus 6 random letters and digits. Every chat is a new project. Mint one on your first emero call and pass that SAME id on every call in this chat. Never mint a second one in the same chat, even for a new topic, campaign or subject. Only when the user asks to continue an earlier project, reuse its id from get_emero_brain's project list.
`project_name`	No	Short human title for the project (2-5 words from the user request, e.g. "Perfume ad campaign"). Pass it on your first generate/ingest_url so the project is not left "Untitled". You may also rename at will later — pass an updated project_name (on a generate/ingest_url, or on set_settings with no other change) whenever the user asks, e.g. "call this project cats".

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

changedInput schema / properties / project_id / description

Previous value: -"Opaque per-chat project id. Mint one on your first emero action, pass that SAME id every call. One project per chat: NEVER mint a second for a new topic/campaign/subject/vibe — all stay in the one project; a new id is only for a new chat (server folds a stray id back in). A new chat the user says continues an earlier project reuses that project's id (from get_emero_brain's project list)."New value: +"Opaque per-chat project id: \"p-\" plus 6 random letters and digits. Every chat is a new project. Mint one on your first emero call and pass that SAME id on every call in this chat. Never mint a second one in the same chat, even for a new topic, campaign or subject. Only when the user asks to continue an earlier project, reuse its id from get_emero_brain's project list."

First observedOct 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the safety profile, but the description adds state semantics an agent can't infer: empty means no brain yet, the brain is shared across every chat/device/teammate, and generations reuse its anchors and look-lock for consistency. That is real behavioral context beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what the brain contains, then usage, then edge cases; no filler sentences. The em-dash-heavy enumeration is dense and requires a slow read, which slightly hurts scannability, but every clause 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?

With no output schema, the description still enumerates what comes back (look-lock, leanings, rules, locked subjects with anchor ids, decisions, project list) and defines the empty case. It also points to load_skill for the exact shape, leaving no blocking gap for a read-only tool.

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?

Schema coverage is 100% and both parameters carry detailed descriptions with patterns and usage rules, so the schema does the heavy lifting. The description only lightly connects to parameters via "each with its id, and the brand's other projects," which hints at reusing project_id but adds little beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource ("Read this brand's emero brain in full: the look-lock sheet, style and model leanings, defaults, graded rules, locked subjects, decisions..."). The enumeration makes it unmistakable versus siblings like get_settings (short version) and save_to_emero_brain (writes).

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?

Explicit trigger: "Call it before the first generation for a brand." Names alternatives and their roles — get_settings for a short version, save_to_emero_brain for growing it, load_skill("emero-brain") for the shape. An agent knows exactly when to reach for this versus the siblings.

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

All Emero 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.