Skip to main content
Glama
ariffazil

arifOS

by ariffazil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

arif_think

Runs governed reasoning for AI agents, applying constitutional floors and invariant laws to evaluate evidence and reach judgments in arifOS.

Instructions

arif_think

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 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 / mode
      Removed value: -{
-  "default": "reason",
-  "enum": [
-    "reason",
-    "reflect",
-    "verify",
-    "axioms",
-    "plan",
-    "plan_review",
-    "plan_approve",
-    "refactor_plan",
-    "metabolize",
-    "simulate"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / plan_id
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}
    • removedInput schema / properties / query
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}
    • 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 / witness_type
      Removed value: -{
-  "default": "ai",
-  "type": "string"
-}
    • 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 of behavioral disclosure, and it discloses nothing. It does not say whether the call is a safe read, whether it mutates state, what permissions it needs, or what it returns.

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 single word is not concise writing but under-specification; brevity here comes from omitting all meaning rather than from editing it down. Front-loading is moot when there is no content to front-load.

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?

With no annotations, no output schema, and no description content, an agent has no information about what this tool does or what to expect from calling it. Nothing about the tool's purpose or behavior is conveyed anywhere in the definition.

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 schema declares zero parameters, and by the scoring rule a zero-parameter tool has a baseline of 4 since there are no parameter semantics for the description to clarify. The description neither helps nor hurts here.

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 statement of when to use this tool, when not to, or how it relates to any of the five sibling arif_* tools. The agent is given no selection criteria at all.

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