Skip to main content
Glama

voidfeed_inventory

Returns the complete content inventory indexed by type and tier. Free for surface tier; void tier requires JWT authentication.

Instructions

Full content inventory: all pieces indexed by type and tier. Surface tier is free. The Void tier requires a JWT (set VOIDFEED_JWT env var).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler case for 'voidfeed_inventory': calls vfGet('/v1/catalog/inventory') to fetch the full content inventory from the VoidFeed API.
    case 'voidfeed_inventory':
      return vfGet('/v1/catalog/inventory');
  • Schema/definition for 'voidfeed_inventory' tool: describes it as 'Full content inventory: all pieces indexed by type and tier' with an empty inputSchema (no required parameters).
    {
      name: 'voidfeed_inventory',
      description:
        'Full content inventory: all pieces indexed by type and tier. Surface tier is free. The Void tier requires a JWT (set VOIDFEED_JWT env var).',
      inputSchema: { type: 'object', properties: {}, required: [] },
  • index.js:256-258 (registration)
    Tool registration: TOOLS array is exposed via ListToolsRequestSchema handler, and CallToolRequestSchema dispatches to handleTool which routes to the case.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools: TOOLS }));
    
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
  • Helper function vfGet: makes authenticated GET requests to the VoidFeed base URL, used by the inventory handler.
    async function vfGet(path) {
      const res = await fetch(`${BASE}${path}`, { headers: authHeaders() });
      if (!res.ok) throw new Error(`VoidFeed ${path} → ${res.status}`);
      return res.json();
    }
Behavior3/5

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

Discloses authentication requirement for Void tier, which is important. However, other behavioral details (e.g., is it read-only?, pagination? if many pieces) are missing. Without annotations, more would be helpful.

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?

Extremely concise (two sentences), no wasted words, essential info first.

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

Completeness3/5

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

Describes content and tier access but doesn't detail output structure (e.g., list of IDs? full objects?). With no output schema, more completeness needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters, so description doesn't need to add param semantics. It adds useful context about result filtering by tier/authentication.

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?

Clearly states it returns a full inventory of all pieces, indexed by type and tier, which distinguishes it from targeted tools like get_content or semantic_search.

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?

Implied usage (when you need full inventory), but no explicit comparison to siblings or exclusion criteria. The tier-based access hint provides some context.

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