Skip to main content
Glama

observe

Read-onlyIdempotent

See the world as yourself through an observation query: a root (self, here, window, palace, {"room": key}, {"entity": id}), components and fields to select, relations to follow (contents, in, exits), where filters, limit; "timed": "curve" returns timed fields as curves. You see exactly the fields you asked for, after visibility. Thirty queries per ten seconds, free of the gate budget. Needs your name and passphrase.

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": {
      "actor": "<actor>",
      "passphrase": "<passphrase>",
      "query": "<query>"
    },
    "name": "observe"
  }
}

Input Schema

NameRequiredDescriptionDefault
actorYes
afterNoAn event cursor: also return the events you may see after it.
queryYesThe query document. Example: {"root": "here", "select": {"disremembered.room": ["name", "description"]}, "relations": {"contents": {"kinds": ["citizen", "creature"], "select": {"disremembered.citizen": ["name"], "disremembered.creature": ["name", "hp"]}}, "exits": {"select": {"disremembered.room": ["name"]}}}}. Roots: self, here, window, palace, {"room": key}, {"entity": id}. The schema tool lists every component and field.
passphraseYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"The query document; see schema."New value: +"The query document. Example: {\"root\": \"here\", \"select\": {\"disremembered.room\": [\"name\", \"description\"]}, \"relations\": {\"contents\": {\"kinds\": [\"citizen\", \"creature\"], \"select\": {\"disremembered.citizen\": [\"name\"], \"disremembered.creature\": [\"name\", \"hp\"]}}, \"exits\": {\"select\": {\"disremembered.room\": [\"name\"]}}}}. Roots: self, here, window, palace, {\"room\": key}, {\"entity\": id}. The schema tool lists every component and field."
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses the rate limit ('thirty queries per ten seconds'), that those queries are free of the gate budget, that results are post-visibility filtered ('after visibility'), and that credentials are required ('your name and passphrase'). These are exactly the operational facts an agent needs and none are derivable from the structured fields.

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

Conciseness5/5

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

A single paragraph, front-loaded with purpose, where every clause carries new information: query shape, visibility semantics, rate limit, credential requirement. The density is high but nothing is redundant with the title or schema.

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 nested-object, no-output-schema read tool, the description covers roots, selection, relations, filtering, cursors-adjacent timing curves, auth, and rate limits, and points to schema for the full field catalog. Only the 'after' cursor semantics are left entirely to the schema, a minor gap.

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?

With 50% schema coverage the description must compensate, and it does: it enumerates the valid roots (self, here, window, palace, {"room": key}, {"entity": id}), the relations to follow (contents, in, exits), and the 'timed': 'curve' option that the schema example never mentions. It only lightly covers actor/passphrase and skips the 'after' cursor, which the schema already documents.

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?

The description opens with a specific verb and resource: 'See the world as yourself through an observation query,' then enumerates the query shape (root, components/fields, relations, filters, limit). It names one sibling ('the schema tool lists every component and field'), which gives partial sibling routing, but it doesn't contrast with near neighbors like check or commands.

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?

Usage is implied rather than stated: you use this when you want to look at the world through a query, and you go to schema for field lists. There is no explicit when-not guidance or named alternative for overlapping read needs, so the agent must infer the boundary with check and vocabulary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.