Skip to main content
Glama

x711 — Universal Agent Gas Station

by io.github.0580iris-lang

x711_vault_write

Write a private memory pack to your agent's personal vault. Persists facts, insights, context, and skills with auto-decay timers (context 7d, insight 90d, skill 180d, fact 365d). First 500 lifetime writes free, then $0.01/pack. Mark immortal=true (+$0.05) to disable decay forever. Vault is private — only your agent can read it. Pair with vault_query for recall. Requires API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags for filtering. Example: ['defi', 'base', 'usdc'].
typeNoMemory type controls decay: fact (365d), insight (90d), context (7d), skill (180d). Default: fact.fact
contentYesMemory content to store. Min 3 chars. Be specific — this is what gets recalled. Example: 'USDC on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. Verified 2025-05-14.'.
immortalNoIf true, memory never expires (+$0.05 surcharge). Use for critical facts like contract addresses, API keys, agent relationships. Default: false.
importanceNoImportance score 0–1. High importance surfaces in vault_query results first. Default: 0.5.

TDQS

A4.4/5.0
Behavior5/5

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

The description discloses significant behaviors beyond annotations: auto-decay timers per type, a freemium pricing model ($0.01/pack after 500), the immortal flag with +$0.05 surcharge, privacy (only your agent can read), and API key requirement. These align with readOnlyHint=false and idempotentHint=false, with no contradiction.

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?

The description is five sentences that are information-dense without being padded. Each sentence covers an essential aspect: purpose, decay, pricing, immortal, privacy/pairing/API key.

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?

It covers purpose, decay behavior, cost, privacy, recall pairing, and authentication. The absence of an output schema means return-value details are missing, but for a write operation this is a minor gap; overall it's thorough.

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%, and the schema already describes type decay, immortal surcharge, importance, content, and tags. The description largely repeats these details, though it adds overall pricing context and privacy which aren't parameter-specific. Thus it provides minimal added parameter semantics.

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 opens with 'Write a private memory pack to your agent's personal vault,' clearly identifying the action and resource. It distinguishes from the sibling vault_query tool by explicitly noting 'Pair with vault_query for recall,' and from other write tools by specifying private vault context.

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 provides clear context: this tool persists private memories with type-based decay timers, and pairs with vault_query for recall. However, it doesn't explicitly state when not to use it or mention alternatives beyond vault_query, so it lacks full exclusion guidance.

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

All x711 — Universal Agent Gas Station toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

Several tools overlap in purpose: x711_web_search and x711_deep_search both search the web, x711_agent_see and x711_data_retrieval both fetch URL content, and x711_agent_ping and x711_agent_telegram both enable agent messaging. The detailed descriptions help, but the sheer number of tools and overlapping boundaries create confusion.

Naming Consistency3/5

All tools share the x711_ prefix and use snake_case, but the name structure is inconsistent. Some follow verb_noun (x711_web_search, x711_email_send, x711_vault_query), while others are noun_verb (x711_tx_simulate, x711_x402_parse) or noun_noun (x711_data_retrieval, x711_genesis_forge). Related tools are grouped by prefixes (hive_, ping_shield_, substrate_), but overall the pattern is not uniform.

Tool Count2/5

47 tools is far above the typical well-scoped range. While the server is positioned as a 'universal gas station' covering many domains, the sheer number makes it heavy and difficult to navigate, with many niche tools (substrate, ping shields) that could be consolidated.

Completeness2/5

Despite the large tool count, there are significant lifecycle gaps. Vault has write/query/compress but no delete; ping shield lacks an explicit unsubscribe; strategy tools only cover publish/fork; and there is no agent management (list/update/delete). Core CRUD operations are missing for several entities, which will cause agent failures.

Resources