Skip to main content
Glama

EVE Frontier Smart Gate Tribe ACL & Dynamic Toll Bytecode Compiler

compile_eve_gate_acl
Read-onlyIdempotent

Compiles EVE Frontier Tribe access lists, diplomatic standings, and surge toll rules into Sui Move Smart Gate AccessPolicy constraints for on-chain jump permissions and LUX/SUI toll schedules.

Instructions

Compiles EVE Frontier Tribe access control lists, diplomatic standings, and surge-pricing toll rules into Sui Move Smart Gate AccessPolicy constraints. Use when configuring on-chain jump permissions and LUX/SUI toll schedules for a player-owned Smart Gate; for calculating optimal multi-system jump routes across existing stargates, use plan_eve_gate_route instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'gate_assembly_id' ('toll_mode' defaults to 'standing_tiered'), supports '?demo=true' or L402 (30 sats), and returns HTTP 400 if invalid.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "gate_assembly_id": "<gate_assembly_id>"
    },
    "name": "compile_eve_gate_acl"
  }
}

Input Schema

NameRequiredDescriptionDefault
toll_modeNoPricing curve applied to non-allied jumpers; defaults to 'standing_tiered' when omitted.
gate_assembly_idYesTarget Smart Gate assembly identifier (e.g. 'gate-lagrange-04').

Output Schema

NameRequiredDescriptionDefault
base_toll_mistYesCalculated base jump toll denominated in MIST/LUX units.
gate_assembly_idYesTarget Smart Gate object identifier.
hostile_block_enforcedYesTrue when hostile tribes are rejected at the Move witness gate.
access_policy_move_structYesCompiled Sui Move AccessPolicy struct definition and entry verifier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.6.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: stateless edge call, 32 KB payload cap, 60 RPM rate limit, demo mode vs L402 (30 sats) payment, and HTTP 400 on invalid input. These are exactly the operational traits an agent needs to avoid failed or throttled calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then usage, then operational constraints — a sensible ordering with no filler sentences. The final clause packs several constraints (size, rate, auth, error code) into one long sentence, which is dense but each element is load-bearing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be described, and the description still covers everything else an agent needs: statelessness, size limit, rate limit, authentication options, and error behavior. For a two-parameter compiler call this is complete.

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 coverage is 100%, with the enum and defaults already documented, so the schema carries the semantic load. The description only restates the 'toll_mode' default ('standing_tiered') and that 'gate_assembly_id' is accepted, adding no new meaning such as identifier format or how toll_mode interacts with standings. Baseline 3 applies.

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?

States a specific verb ('Compiles') plus three concrete resources (Tribe ACLs, diplomatic standings, surge-pricing toll rules) and names the exact output artifact (Sui Move Smart Gate AccessPolicy constraints). It explicitly distinguishes itself from the nearest sibling, plan_eve_gate_route, so an agent can select between them without opening either schema.

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?

Gives an explicit when-to-use clause ('configuring on-chain jump permissions and LUX/SUI toll schedules for a player-owned Smart Gate') and an explicit when-not/alternative clause routing route-planning queries to plan_eve_gate_route. Both the positive and negative selection conditions are stated.

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