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_session_pack

Idempotent

Load a compact session-start context capsule (<350 tokens) returning active contradiction-free project/global beliefs, recent actions, root-cause warnings, and verified skills. Call once at cold start instead of oxyo_recall; use oxyo_recall for targeted mid-session searches.

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_session_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
focusNoOptional current task focus query used to rank relevant rules and warnings.
scopeNoProject or repository scope identifier (e.g. 'oxyo', 'backend', or 'global').
auto_consolidateNoAutomatically archive redundant older episodes when episode count exceeds threshold.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / auto_consolidate / description
      Previous value: -"Automatically compact redundant older episodes when above threshold"New value: +"Automatically archive redundant older episodes when episode count exceeds threshold."
    • changedInput schema / properties / focus / description
      Previous value: -"Optional current task focus query to rank rules and warnings"New value: +"Optional current task focus query used to rank relevant rules and warnings."
    • changedInput schema / properties / scope / description
      Previous value: -"Optional project/repo scope (e.g. 'oxyo', 'omniamus', or 'global')"New value: +"Project or repository scope identifier (e.g. 'oxyo', 'backend', or 'global')."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description adds real context beyond annotations by disclosing the token budget and the exact content classes returned, which the annotations do not convey. However, annotations declare readOnlyHint=false while the description frames the tool purely as a 'load'; it never mentions that the default auto_consolidate=true can archive older episodes, so the non-read-only side effect is left unexplained in prose.

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 sentences, zero filler, with the primary identity and payload budget front-loaded before the sibling routing clause. Every clause carries actionable information.

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?

With no output schema, the description carries the burden of describing return values and does so by enumerating the content categories, which is sufficient for an agent to know what to expect. The only gap is the undisclosed archive side effect of auto_consolidate, which lives in the schema but is not reconciled with the 'load' framing.

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 all three parameters carry their own descriptions, so the baseline is 3. The description adds meaning only indirectly, via 'active' and 'contradiction-free' implying how focus-based ranking filters results, without documenting any parameter itself.

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 ('Load a compact session-start context capsule') and enumerates exactly what it returns: contradiction-free beliefs, recent actions, root-cause warnings, and verified skills. It also bounds the payload at <350 tokens, which distinguishes it sharply from the bulk-recall sibling.

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?

Explicit routing: 'Call once at cold start instead of oxyo_recall' plus the inverse condition 'use oxyo_recall for targeted mid-session searches.' Both the when and the when-not are stated with the named alternative, leaving nothing to inference.

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