Skip to main content
Glama

tcai_emotion_appraise

Convert raw threat, novelty, reward, and controllability signals into PAD emotional coordinates with inertia. Use it to model affective state in bio-hybrid simulations.

Instructions

Appraise raw signals into PAD emotional space (Mehrabian) with inertia

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

Input Schema

NameRequiredDescriptionDefault
threatNo
noveltyNo
rewardSignalNo
controllabilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.8/5.0
Behavior3/5

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

The annotations already declare a non-read-only, non-idempotent, non-destructive, closed-world operation, so the safety profile is largely covered. The description adds one genuine behavioral trait beyond them — 'with inertia' implies prior emotional state influences the result, which is real context — but it omits whether internal state is mutated, ordering/persistence semantics, and any rate or calibration caveats.

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?

A single front-loaded clause with no wasted words, which is structurally good. But for a four-parameter tool with zero schema documentation this brevity crosses into under-specification rather than genuine conciseness.

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

Completeness2/5

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

For a tool that transforms four appraisal inputs into a PAD state with hysteresis, the description leaves the input semantics, the output shape (no output schema exists), and the effect on internal TCAI state all unexplained. Annotations cover safety only; the descriptive gap remains substantial.

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 four parameters, so the description carries the full burden — and it adds nothing. It never explains that threat/novelty/controllability are normalized 0–1 appraisal axes while rewardSignal spans −1 to 1, nor how they combine into PAD. Names alone are suggestive but not sufficient.

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 ('Appraise') and a named target/output space ('PAD emotional space (Mehrabian)'), which is more informative than a tautology. It does not, however, distinguish this from sibling appraisal/state tools like tcai_self_model or tcai_curiosity, and it never says what the 'raw signals' are.

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?

No when-to-use guidance, no prerequisites, no indication of where this sits in the TCAI cycle, and no alternatives named among the many tcai_* siblings. The agent must infer invocation context entirely from the tool name.

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