Skip to main content
Glama
ariffazil

arifOS

by ariffazil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

arif_judge

Adjudicates AI agent actions against constitutional floors and invariant laws, providing a judgment for governance decisions.

Instructions

arif_judge

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 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
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / actor_id
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}
    • removedInput schema / properties / authority_token
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}
    • removedInput schema / properties / blast_radius
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / domain
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / epistemic_state
      Removed value: -{
-  "default": "UNKNOWN",
-  "type": "string"
-}
    • removedInput schema / properties / evidence
      Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}
    • removedInput schema / properties / intent
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / measurement
      Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}
    • removedInput schema / properties / requested_capability
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / reversibility_level
      Removed value: -{
-  "type": "string"
-}
    • 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 / required
      Removed value: -[
-  "actor",
-  "intent",
-  "requested_capability",
-  "domain",
-  "reversibility_level",
-  "blast_radius"
-]
    • 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. Whether this judges, mutates state, requires auth, or has side effects is entirely unknown.

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?

A single bare token is not conciseness but under-specification. There is no sentence structure or front-loading to evaluate, and no information is conveyed.

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 five sibling arif_* tools, the description provides no differentiation, no behavior, and no usage context. It is completely inadequate for correct selection.

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. There is nothing for the description to clarify, though it also adds nothing 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?

No when-to-use guidance, no alternatives, no context for selecting this over the other arif_* tools. The agent is left with zero routing information.

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