USERDATA

log

Record decisions, findings, and other research events by session with structured details to preserve a traceable history of what happened.

Instructions

Records what happened, e.g. event_type "decision" or "finding".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>",
      "event_type": "<event_type>",
      "details": "<details>"
    },
    "name": "log"
  }
}

Input Schema

Name	Required	Description	Default
`details`	Yes
`event_type`	Yes
`session_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 8, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and delivers almost none of it: it doesn't say whether entries persist, whether they are scoped to the session, whether logging is idempotent, or what happens on failure. An output schema exists, so return values need not be explained, but the write semantics and session binding are left undisclosed.

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

Conciseness3/5

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

It is a single short sentence with the key concept front-loaded, which is efficient. But the brevity comes at the cost of under-specification rather than trimming redundancy, so it is concise without being informative.

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?

Given that an output schema exists, the description needn't cover return values, lowering the bar. Still, for a three-required-parameter write tool with a nested details object and zero annotation coverage, the missing session scoping and details-structure guidance leaves real gaps.

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

Parameters2/5

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

Schema description coverage is 0% across three required parameters. The description only illuminates event_type with two example values; session_id's relationship to start_session and the expected contents/shape of the free-form nested details object are entirely undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb "Records" plus "what happened" identifies a generic event-logging tool, and the examples ("decision", "finding") hint at the kinds of entries expected. However, it does not distinguish this from close siblings like add_note, tag, or history, so an agent cannot confidently pick it over those from the description alone.

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

Usage Guidelines2/5

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

There is no guidance on when to log versus when to use add_note or tag, no mention of required preconditions (e.g. an active session from start_session), and no exclusions. The agent must infer usage entirely.

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

log