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_skill_invoke

Read-onlyIdempotent

List registered Python skills (action='list') or execute a named skill (action='execute') with arguments in isolation, returning its deterministic return value. Use to run already-verified skills; call oxyo_skill_register first to create a new skill.

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

Input Schema

NameRequiredDescriptionDefault
argsNoPositional JSON arguments passed to the skill entrypoint when action='execute'.
nameNoRegistered skill name to execute (required when action='execute').
actionNoChoose 'list' to browse available skills or 'execute' to run `name` with `args`.list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"Choose 'list' to browse available skills or 'execute' to run `name` with `args`."
    • addedInput schema / properties / args / description
      Added value: +"Positional JSON arguments passed to the skill entrypoint when action='execute'."
    • addedInput schema / properties / name / description
      Added value: +"Registered skill name to execute (required when action='execute')."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description's contribution is 'in isolation' and 'deterministic return value', which reinforce that execution is sandboxed and repeatable. What 'isolation' actually means (resource limits, timeouts, filesystem/network access, error propagation) is not disclosed, which matters a lot for a tool that executes code.

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, both front-loaded: the capability and its two modes come first, the prerequisite/alternative second. No filler, no redundancy.

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 only three fully documented parameters and no output schema, the description covers modes, the register-first prerequisite and execution isolation, which is enough to invoke it correctly. A brief note on failure behavior for execute (bad name, exception in skill, arg validation) would close the remaining gap.

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%, so all three parameters (action, name, args) are already documented including the enum values and defaults. The description restates the action modes and repeats that name/args apply on execute, adding little semantics beyond the schema; the one extra hint is that execution happens in isolation.

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

Purpose4/5

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

The description names both concrete operations (list registered skills; execute a named skill with arguments) plus the return contract ('deterministic return value'), so an agent knows exactly what the tool does. It falls short of a 5 because nothing distinguishes it from relevant siblings such as oxyo_verify_python, which an agent might otherwise reach for.

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

Usage Guidelines4/5

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

It gives a clear positive usage rule ('Use to run already-verified skills') and routes the agent to the sibling that must be called first ('call oxyo_skill_register first to create a new skill'). It does not state any when-not condition, e.g. what to do instead when a skill fails verification or when code has not yet been registered.

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