Skip to main content
Glama
server-noonien

server-noonien

Official

Set Observations

set_observations
Destructive

Write a current key: value fact on an entity, replacing any existing observations for that key so stale values do not survive. Use it when a version or status changes over time.

Instructions

Keep one fact current: write key: value on an entity, replacing every observation that key already holds, so a drifted twin cannot survive. Use it instead of update_observations when the value changes over time — a version, a status — and you should not have to remember its previous text. An observation belongs to a key when it is exactly the key or starts with the key, a colon and a space, and a key may not itself contain a colon followed by a space. A missing entity fails as add_observations does: create it with create_entities first.

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": {
      "entries": "<entries>"
    },
    "name": "set_observations"
  }
}

Input Schema

NameRequiredDescriptionDefault
entriesYesOne entry per fact

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructive=true and readOnly=false, but the description adds what is actually destroyed (every observation the key holds), the exact matching rule ("exactly the key or starts with the key, a colon and a space"), the key-format constraint, and the missing-entity failure mode. The one unresolved point is repeated invocation: the set-style replacement implies calling twice with the same value leaves the same state, which sits awkwardly with idempotentHint=false, and the description does not address history/versioning effects that the read_history/read_changes siblings hint at.

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?

Four sentences, front-loaded with the purpose and immediately followed by the sibling comparison, then the matching rule, then the failure mode. Every sentence carries information; only the flourish "so a drifted twin cannot survive" is close to expendable.

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?

An output schema exists, so return values need no explanation, and the description covers purpose, alternative selection, key matching, and the missing-entity error path. What remains unstated is batch behavior for multi-entry calls (atomic vs per-entry failure) and whether repeated sets leave an audit trail, which matter for a destructive multi-fact write.

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 coverage is 100%, so the baseline is 3, but the description goes beyond the schema by defining what counts as a match for key (exact key, or key followed by colon+space) and forbidding colon+space inside a key. That is a substantive semantic constraint the schema does not state.

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?

"Keep one fact current: write key: value on an entity, replacing every observation that key already holds" gives a specific verb, resource, and write semantics, and it explicitly separates this tool from update_observations. An agent can tell exactly what this does without opening the schema.

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

Usage Guidelines5/5

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

Names the alternative (update_observations) and the exact condition that selects this tool: values that drift over time and where the caller should not have to supply prior text. It also gives a prerequisite path for the failure case: create the entity with create_entities first.

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