Skip to main content
Glama

record_thinking_event

Record thinking signals to personalize Metis. Each event shapes your profile for tailored suggestions and agent routing.

Instructions

Record one signal about how you think and work, to personalise Metis.

Each event is a small piece of evidence — you acted on a brainstorm, rated
an idea highly, flagged an agent's output — that feeds your evolving
"thinking profile". Over time these signals let Metis tailor its routing,
suggestions, and tone to your preferences. Call it whenever a meaningful
preference moment occurs; read the accumulated profile with
get_thinking_profile.

Args:
    event_type: The kind of signal. Must be one of: "brainstorm_acted_on",
        "brainstorm_ignored", "idea_rated_high", "idea_linked_project",
        "journal_revisited", "agent_output_accepted", "agent_output_flagged".
    source_type: Domain or category the signal belongs to (e.g. "biology").
        Optional; defaults to empty.
    content_id: ID of the related content record (idea, journal entry, etc.)
        if applicable. Optional; defaults to 0 (none).
    agent_slug: Agent identifier this signal relates to, used for the
        "agent_output_*" event types. Optional.
    context: Free-text note giving context for the event. Optional.

Returns:
    A confirmation that the signal was recorded, or an error listing the
    valid event types if an invalid one was supplied.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_typeYes
source_typeNo
content_idNo
agent_slugNo
contextNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations; description discloses it records a signal, is non-destructive, and returns confirmation or error. Doesn't detail side effects or auth needs, but sufficient given simplicity.

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?

Well-structured with paragraphs and an Args section. Front-loaded with purpose. Each sentence provides useful information, though slightly verbose.

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?

Covers all 5 parameters, return value, and error case. Output schema exists. Completeness is good for a moderate-complexity tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Each parameter is thoroughly documented in the description text, including valid values for event_type, defaults, and optionality. Adds significant value over the bare 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?

States 'Record one signal about how you think and work' with a clear verb, resource, and purpose. Distinguishes from sibling get_thinking_profile by mentioning it.

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?

Provides guidance: 'Call it whenever a meaningful preference moment occurs.' Lists event types and references get_thinking_profile. Lacks explicit when-not or comparison to reset_thinking_profile.

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/SVerITG/Metis_PH'

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