Skip to main content
Glama
Sign In
VoidFeed

VoidFeed

Official
by voidfeedai-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

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).

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": "voidfeed_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
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.

Deploy Server

Other Tools