Skip to main content
Glama
ariffazil

arifOS

by ariffazil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

arif_observe

Captures and reports runtime observations from AI agent sessions, supporting evidence-based reasoning and constitutional compliance checks.

Instructions

arif_observe

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv2026.10.16
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +true
    • removedInput schema / properties / _envelope
      Removed value: -{
-  "default": null,
-  "title": "Envelope"
-}
    • removedInput schema / properties / actor_id
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}
    • removedInput schema / properties / layers
      Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}
    • removedInput schema / properties / mode
      Removed value: -{
-  "default": "search",
-  "enum": [
-    "search",
-    "fetch",
-    "hybrid_discovery",
-    "ingest",
-    "compass",
-    "atlas",
-    "entropy_dS",
-    "vitals"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / query
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}
    • removedInput schema / properties / result_limit
      Removed value: -{
-  "default": 10,
-  "type": "integer"
-}
    • removedInput schema / properties / session_id
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}
    • removedInput schema / properties / session_token
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}
    • removedInput schema / properties / url
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. Addedv0.1.1

TDQS

D1.6/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden, and it discloses nothing about behavior — no side effects, no state changes, no cost, no prerequisites. The agent cannot tell whether this observes, mutates, or merely reads.

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

Conciseness2/5

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

The text is short but only because it is under-specified, not because it is concise. A bare name is not a front-loaded description — no information is conveyed at all.

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

Completeness1/5

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

For a tool sitting in a family of six similarly named arif_* tools, the description is completely inadequate: no purpose, no usage context, no behavioral disclosure, and no output schema to compensate. An agent cannot call this correctly with any confidence.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to add; baseline 4 applies. The empty schema and additionalProperties:true mean an agent learns only that no declared inputs exist.

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

Purpose1/5

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

Tautological: description restates name/title.

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

Usage Guidelines1/5

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

There is no guidance whatsoever on when to use this tool, when not to, or which sibling to prefer. An agent has no basis for selecting arif_observe over arif_think or arif_judge.

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

Deploy Server

Other Tools