Skip to main content
Glama
TrialRun MCP

TrialRun MCP

by kostadindev

Record an AI-literacy habit moment

record_moment

Log a coaching moment for one of three habits—checking AI output, keeping a judgment call, or protecting restricted data—with outcome and a redacted note.

Instructions

For a coaching skill: log a moment for one of three habits. habit: "check" (verifying AI output), "decide" (keeping a judgement call), "protect" (keeping restricted data out). outcome: "did" (the user did it unprompted), "prompted" (after a coaching note), "missed". Restricted values in the note are redacted before storage.

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": {
      "habit": "<habit>",
      "outcome": "<outcome>",
      "note": "<note>"
    },
    "name": "record_moment"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYesOne sentence describing what happened, without personal data
habitYes
outcomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one meaningful behavior: restricted values in the note are redacted before storage, which tells the agent writes are sanitized. It does not say what a successful call returns, whether entries are mutable or auditable, or whether any consent/permission is required for logging a user's behavior — gaps that matter for a write tool with zero annotation coverage.

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 the purpose, then the enums with compact parenthetical glosses that each earn their place. The 'For a coaching skill:' prefix is slightly awkward but does real work by scoping the tool; nothing is redundant.

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 3-parameter write tool with no output schema and no annotations, the description covers purpose, all enum semantics, and the redaction behavior, which is most of what an agent needs. It falls short only on return/confirmation behavior and any permission or consent preconditions.

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?

Schema description coverage is only 33% (only 'note' is documented), so the description must compensate, and it largely does: it defines all three habit values ('check' = verifying AI output, 'decide' = keeping a judgement call, 'protect' = keeping restricted data out) and all three outcome values ('did' unprompted, 'prompted' after a coaching note, 'missed'). The only thing left to the schema is note length and format constraints.

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

Purpose4/5

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

States a specific verb and resource ('log a moment') plus the bounded domain ('one of three habits') and enumerates those habits. An agent can tell this is a write-side logging tool, distinct from the read-oriented siblings (read_file, get_audit_log, get_report), though the description never names a sibling to contrast with explicitly.

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

Usage Guidelines3/5

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

The opening 'For a coaching skill' frames the context in which the tool applies, which is real usage guidance. However, it offers no when-not conditions and no alternatives, so an agent must infer the boundaries from the sibling set on its own.

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