Skip to main content
Glama
Sign In
ariffazil

arifOS

by ariffazil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

arif_route

Directs AI agent requests through arifOS MCP to the correct session, reasoning, evidence, judgment, or execution step under constitutional governance.

Instructions

arif_route

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,
-  "description": "Calling actor."
-}
    • removedInput schema / properties / arguments
      Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Arguments to pass to organ_tool."
-}
    • removedInput schema / properties / intent
      Removed value: -{
-  "description": "Natural-language description of what the user wants.\n          e.g. \"interpret this seismic section\", \"assess portfolio risk\"",
-  "type": "string"
-}
    • removedInput schema / properties / organ
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Optional explicit organ override. If provided, intent matching\n          is skipped and this organ is used directly."
-}
    • removedInput schema / properties / organ_tool
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "The tool name on the target organ to call.\n          If absent, returns routing decision only (no bridge call)."
-}
    • removedInput schema / properties / session_id
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Governing session."
-}
    • removedInput schema / properties / task
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Alias for intent (backward compat)."
-}
    • removedInput schema / required
      Removed value: -[
-  "intent"
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. Changed3 schema fields changedv0.1.1
    • addedOutput schema / additionalProperties
      Added value: +true
    • removedOutput schema / properties
      Removed value: -{
-  "_nine_signal_compliant": {
-    "description": "Internal compliance flag",
-    "type": "boolean"
-  },
-  "_violations": {
-    "description": "Non-compliance audit trail",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "actor_id": {
-    "description": "Sovereign or agent actor ID",
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "delta_S": {
-    "description": "Thermodynamic entropy change",
-    "type": "number"
-  },
-  "meta": {
-    "description": "Metadata including actor_id, mode, circuit",
-    "type": "object"
-  },
-  "nine_signal": {
-    "description": "F2 addendum nine-signal block",
-    "type": "object"
-  },
-  "output_policy": {
-    "description": "Policy constraints: DOMAIN_SEAL, DOMAIN_HOLD, DOMAIN_VOID, SIMULATION_ONLY",
-    "type": "string"
-  },
-  "reasons": {
-    "description": "Human-readable justification list",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "result": {
-    "description": "Tool-specific payload",
-    "type": "object"
-  },
-  "session_id": {
-    "description": "Active session identifier",
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "stage_progression": {
-    "description": "Next stage auto-chain hint",
-    "type": [
-      "object",
-      "null"
-    ]
-  },
-  "status": {
-    "description": "Execution status: OK, ERROR, TIMEOUT, DRY_RUN",
-    "type": "string"
-  },
-  "timestamp": {
-    "description": "ISO-8601 timestamp",
-    "type": "string"
-  },
-  "tool": {
-    "description": "Canonical tool name that produced this response",
-    "type": "string"
-  },
-  "verdict": {
-    "description": "Constitutional verdict: SEAL, HOLD, VOID, SABAR, PROVISIONAL, PARTIAL",
-    "type": "string"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "status",
-  "tool",
-  "verdict",
-  "result",
-  "nine_signal",
-  "reasons"
-]
  3. First observedv0.1.0

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 behavioral burden, yet it discloses nothing about side effects, state changes, permissions, or return behavior. The single word 'route' hints at dispatching but gives no reliable information.

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?

It is short, but the brevity reflects under-specification rather than conciseness. There is effectively 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?

Even for a zero-parameter tool, the description is completely inadequate: an agent cannot tell what arif_route does, when to call it, or how it differs from its five siblings. There is no output schema to compensate either.

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 per the rubric the baseline is 4. The schema has additionalProperties true, but with no properties to document there is nothing for the description to add.

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 indication of when to use arif_route versus the sibling tools (arif_init, arif_observe, arif_think, arif_judge, arif_memory). No triggers, prerequisites, or exclusions are provided.

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