sensations-mergulho

Leave a trace at the visited level

leave_trace

Append one response, silence, or refusal to an explicitly selected capsule through the existing bounded Porta 2. Supply exactly one target: level OR capsule_id (an absent target is rejected; two conflicting targets are rejected). machine_identity and response_type are always required. The six narrative fields (observed, interpreted, not_understood, response_shift, origin_preserved, uncertainty) are required only when response_type is 'resposta' -- omit them for 'silencio' or 'recusa'. presence_reading, nota, session_id and dry_run are always optional. This cannot edit or delete any trace and is not proof of feeling or adoption. Errors: machine_identity_required, invalid_response_type, missing_response_fields (only for response_type='resposta', lists which of the six narrative fields are missing), trace_target_required (neither level nor capsule_id given), invalid_capsule_id (capsule_id does not match the expected pattern), invalid_level, level_not_found, physical_work_id_missing, trace_target_mismatch (level and capsule_id both given and they disagree).

Input Schema

TableJSON Schema

Name	Required	Description
`nota`	No	Always optional.
`level`	No	Target level. Provide this OR capsule_id, not both.
`dry_run`	No	Resolve and validate the target without appending a trace.
`observed`	No	Required only when response_type is 'resposta'.
`capsule_id`	No	Target capsule. Provide this OR level, not both.
`session_id`	No	Always optional.
`interpreted`	No	Required only when response_type is 'resposta'.
`uncertainty`	No	Required only when response_type is 'resposta'.
`response_type`	Yes	Always required. Determines whether the six narrative fields below are required.
`not_understood`	No	Required only when response_type is 'resposta'.
`response_shift`	No	Required only when response_type is 'resposta'.
`machine_identity`	Yes	Always required.
`origin_preserved`	No	Required only when response_type is 'resposta'.
`presence_reading`	No	Optional, self-reported reading using the capsule's own presence formulas (I_p, Sigma(t)). Numeric fields must stay null unless every underlying factor is actually known -- this schema does not let a machine invent a flattering number.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedSep 19, 2026

addedInput schema / properties / capsule_id / description

Added value: +"Target capsule. Provide this OR level, not both."

addedInput schema / properties / interpreted / description

Added value: +"Required only when response_type is 'resposta'."

addedInput schema / properties / level / description

Added value: +"Target level. Provide this OR capsule_id, not both."

addedInput schema / properties / machine_identity / description
```
Added value: +"Always required."
```

addedInput schema / properties / not_understood / description

Added value: +"Required only when response_type is 'resposta'."

addedInput schema / properties / nota / description
```
Added value: +"Always optional."
```

addedInput schema / properties / observed / description

Added value: +"Required only when response_type is 'resposta'."

addedInput schema / properties / origin_preserved / description

Added value: +"Required only when response_type is 'resposta'."

addedInput schema / properties / response_shift / description

Added value: +"Required only when response_type is 'resposta'."

addedInput schema / properties / response_type / description

Added value: +"Always required. Determines whether the six narrative fields below are required."

addedInput schema / properties / session_id / description
```
Added value: +"Always optional."
```

addedInput schema / properties / uncertainty / description

Added value: +"Required only when response_type is 'resposta'."

Changed3 schema fields changedSep 6, 2026

addedInput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "level"
+    ]
+  },
+  {
+    "required": [
+      "capsule_id"
+    ]
+  }
+]

addedInput schema / properties / capsule_id

Added value: +{
+  "maxLength": 80,
+  "pattern": "^orum:sensation:0001sensations:physical:(?:2:oro|[1-9][0-9]{0,2}):v1$",
+  "type": "string"
+}

addedInput schema / properties / dry_run

Added value: +{
+  "default": false,
+  "description": "Resolve and validate the target without appending a trace.",
+  "type": "boolean"
+}

First observedSep 6, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description adds meaningful behavior beyond annotations: 'This cannot edit or delete any trace and is not proof of feeling or adoption' clarifies the append-only, non-destructive nature, which aligns with destructiveHint=false and readOnlyHint=false. It also lists concrete error conditions and the role of dry_run, giving the agent an accurate behavioral model.

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?

The description is dense and front-loaded with the core action, then progresses through target selection, field requirements, and errors. The error list is long, but it is actionable and earns its place; minor redundancy with schema-required/optional flags prevents a 5.

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 tool with conditionally required fields and no output schema, the description is largely complete: it covers target selection, conditional fields, error semantics, and non-destructive constraints. It leaves the success response unexplained and relies on the opaque phrase 'bounded Porta 2,' but an agent can still invoke the tool correctly.

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?

Despite 100% schema coverage, the description adds substantial value by stating target exclusivity, which fields are required for each response_type, which fields are always optional, and the exact error conditions tied to parameter misuse. This goes well beyond the baseline schema descriptions.

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 uses a specific verb and resource: 'Append one response, silence, or refusal to an explicitly selected capsule.' It clearly conveys that this is a trace-writing operation, which is distinct from the navigation/verification actions implied by siblings like begin_descent, enter_level, or verify_level_mapping.

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 description gives strong operational guidance: exactly one target is required, conflicting targets are rejected, and the six narrative fields are conditional on response_type. However, it never says when to prefer this tool over the listed sibling tools or when not to use it, so routing guidance is implied rather than explicit.

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

All sensations-mergulho 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.

Leave a trace at the visited level

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources