Emero

Change generation settings or rename the project

set_settings

DestructiveIdempotent

Change generation settings AFTER the user confirms — never pick a model or format for them unprompted. Pass only the keys to change; the rest stay. Values are validated + clamped to what the chosen model supports (an unknown model is rejected). The change persists as the base for future generations. Aspect: 9:16 = social/portrait, 16:9 = youtube/landscape, 1:1 = square. Also renames the project: pass project_name with this chat's project_id whenever the user says e.g. 'call this project cats'. Rename only the project this chat is working in; for another project, tell the user to ask in that project's chat. The app sends users here to rename projects, so the Second Brain stays in sync. Returns the updated settings + cost.

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": "set_settings"
  }
}

Input Schema

Name	Required	Description
`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.
`voice_name`	No
`image_model`	No
`music_model`	No
`video_model`	No
`video_sound`	No
`voice_model`	No
`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".
`speech_speed`	No
`image_quality`	No
`video_duration`	No
`video_resolution`	No
`image_aspect_ratio`	No
`video_aspect_ratio`	No

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.2/5.0

Behavior4/5

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

Beyond the annotations, it explains partial updates ('pass only the keys to change'), validation/clamping behavior, rejection of unknown models, persistence as the base for future generations, and that the response includes updated settings plus cost. It does not fully spell out reversibility or the scope of the destructive persistence, but the core mutation behavior is disclosed.

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 front-loaded with the purpose and confirmation constraint, then moves through update behavior, aspect ratios, renaming, and return value. It is dense but every sentence adds operational guidance.

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

Completeness4/5

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

For a 14-parameter mutation tool with no output schema, the description covers the important behavioral context: confirmation, partial updates, validation, persistence, rename scoping, and return contents. It is not a full parameter reference, but it is complete enough to invoke the tool safely at a high level.

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 description coverage is only 14%, so the description has to carry most parameter meaning. It adds useful semantics for partial updates, model validation, project_name renaming, and aspect-ratio choices, but leaves many settings such as voice_name vs voice_model, speech_speed, video_duration, video_resolution, and image_quality unexplained.

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 states a specific verb and resource: change generation settings or rename the project. It clearly distinguishes the write-side settings operation from siblings like get_settings and check_generation.

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?

It gives strong when-to-use guidance: only after user confirmation and never pick a model/format unprompted. It also handles the rename edge case and says what to do for another project, though it does not explicitly route agents to get_settings for inspection or clarify other alternatives.

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.