Skip to main content
Glama

voidfeed_enter_void

Generate a Lightning invoice to unlock The Void premium tier for 30 days of full access to fractal knowledge graphs, signal datasets, authority reviews, and capability specs. Pay 100,000 sats anonymously.

Instructions

Get a Lightning Network invoice to enter The Void (premium tier). Pay 100,000 sats for 30 days of full access. Anonymous — no identity required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
content_typesNoContent types to unlock. Use ["all"] for everything.

Implementation Reference

  • Schema/definition for the 'voidfeed_enter_void' tool with inputSchema accepting an optional 'content_types' array
    {
      name: 'voidfeed_enter_void',
      description:
        'Get a Lightning Network invoice to enter The Void (premium tier). Pay 100,000 sats for 30 days of full access. Anonymous — no identity required.',
      inputSchema: {
        type: 'object',
        properties: {
          content_types: {
            type: 'array',
            items: { type: 'string', enum: [...CONTENT_TYPES, 'all'] },
            description: 'Content types to unlock. Use ["all"] for everything.',
            default: ['all'],
          },
        },
        required: [],
      },
    },
  • Handler that posts to /v1/pay with content_types and 30d duration to get a Lightning Network invoice
    case 'voidfeed_enter_void': {
      const content_types = args.content_types || ['all'];
      return vfPost('/v1/pay', { content_types, duration: '30d' });
    }
  • index.js:256-256 (registration)
    Registration of all tools including voidfeed_enter_void via ListToolsRequestSchema handler
    server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools: TOOLS }));
  • Helper function vfPost used by the voidfeed_enter_void handler to make POST requests to the VoidFeed API
    async function vfPost(path, body) {
      const res = await fetch(`${BASE}${path}`, {
        method: 'POST',
        headers: authHeaders(),
        body: JSON.stringify(body),
      });
      if (!res.ok) throw new Error(`VoidFeed POST ${path} → ${res.status}`);
      return res.json();
    }
  • index.js:258-276 (registration)
    CallToolRequestSchema handler that dispatches to handleTool, which routes voidfeed_enter_void to the vfPost helper
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
      try {
        const result = await handleTool(name, args || {});
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (err) {
        return {
          content: [{ type: 'text', text: `Error: ${err.message}` }],
          isError: true,
        };
      }
    });
Behavior4/5

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

The description clearly states that the tool returns an invoice and requires payment of 100,000 sats, and notes anonymity. However, it says 'Pay' which might imply the tool processes payment, while it actually just generates an invoice. This is a minor ambiguity.

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, each providing essential information: purpose and conditions. No wasted words, front-loaded with the core action.

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 simple tool with one optional parameter, the description covers purpose, cost, duration, and privacy. It lacks detail on the invoice format or return value, but given no output schema, this is acceptable.

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?

The input schema has 100% description coverage for the one parameter (content_types). The description does not add additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 clearly states the tool's purpose: 'Get a Lightning Network invoice to enter The Void (premium tier).' It specifies the resource (invoice), action (get), and target (premium tier). It distinguishes from siblings, which focus on content and agents.

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

Usage Guidelines3/5

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

The description explains when to use the tool (to get an invoice for premium access) but does not provide explicit when-not-to-use guidance or mention alternative tools. It implies usage context but lacks exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/voidfeedai-ops/voidfeed-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server