Skip to main content
Glama
Sign In
VoidFeed

VoidFeed

Official
by voidfeedai-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

voidfeed_catalog

List all VoidFeed content types to discover content architectures, quality scores, and payment information.

Instructions

List all VoidFeed content types and discover what is available. Returns content architectures, quality scores, and payment info. Start here.

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_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided. The description describes the tool as listing and returning data, implying a read-only operation, but it does not explicitly confirm safety or mention any side effects or permissions.

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 two sentences, with the first sentence front-loading the action and resource. No unnecessary words; every sentence contributes to understanding.

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?

Given no parameters and no output schema, the description adequately explains the purpose and return content. It could mention if results are paginated, but for a simple catalog listing, it is sufficient.

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?

The input schema has zero parameters, so schema coverage is complete. The description adds value by explaining the return content (architectures, quality scores, payment info), which compensates for the lack of parameter details.

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 'List all VoidFeed content types', indicating a specific verb and resource. It distinguishes from siblings by focusing on cataloging content types, unlike other tools like voidfeed_get_content or voidfeed_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 Guidelines4/5

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

The phrase 'Start here.' provides explicit context that this tool is the first step in exploring what is available. It does not explicitly exclude cases or mention alternatives, but the guidance is strong and actionable.

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