Skip to main content
Glama
Sign In

Oxyo (oxyo.si) — Cut Coding Agent Token & Quota Burn by up to 72%

by io.github.Eno654
OverviewDiscussionsAdmin

oxyo_belief_revisions

Read-onlyIdempotent

Retrieve the immutable audit log of superseded beliefs paired with the newer claims that replaced them. Use to inspect historical rule changes and contradiction resolutions; use oxyo_recall for active beliefs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "oxyo_belief_revisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of recent belief revision entries to return (1..100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of recent belief revision entries to return (1..100)."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds that the log is immutable and that entries pair a superseded belief with its replacement, which is real behavioral context beyond the structured fields. It stops short of describing ordering or entry fields, keeping it below a 5.

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?

Two tight sentences with the core purpose front-loaded and the disambiguation clause following; nothing is redundant or padded.

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 single-parameter read-only tool with rich annotations, the description is nearly complete: it says what is returned conceptually (superseded claim plus replacement). A minor gap is the lack of detail on ordering or recency semantics for the returned entries.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single `limit` parameter is fully documented in the schema (default 20, range 1..100), so the description carries no burden here. It adds no meaning beyond the schema, which is the baseline 3 case.

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

Purpose5/5

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

The description names a specific verb and resource ("Retrieve the immutable audit log of superseded beliefs paired with the newer claims that replaced them") and explicitly contrasts it with the sibling that handles active beliefs, so an agent can distinguish it without inspecting schemas.

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

Usage Guidelines5/5

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

It states both the positive use case ("inspect historical rule changes and contradiction resolutions") and the alternative for a different need ("use `oxyo_recall` for active beliefs"), giving an explicit routing rule.

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

All Oxyo (oxyo.si) — Cut Coding Agent Token & Quota Burn by up to 72% toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources