Skip to main content
Glama

vybsly_knowledge

Search the web and an encyclopedia in one call. Retrieve results tagged by source for factual answers needing both breadth and authority.

Instructions

Federated search: web index + structured encyclopedia in one call. Returns results tagged by source (vybsly/vybpedia). Best for factual questions needing both breadth (web) and authority (encyclopedia).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query (required)
limitNoTotal max results (default 10)
strictNo
researchNo

Implementation Reference

  • Input schema definition for the vybsly_knowledge tool. Defines query (required), limit, strict, and research parameters.
    {
      name: 'vybsly_knowledge',
      description: 'Federated search: web index + structured encyclopedia in one call. Returns results tagged by source (vybsly/vybpedia). Best for factual questions needing both breadth (web) and authority (encyclopedia).',
      inputSchema: {
        type: 'object',
        properties: {
          query: { type: 'string', description: 'Search query (required)' },
          limit: { type: 'number', description: 'Total max results (default 10)', default: 10 },
          strict: { type: 'boolean' },
          research: { type: 'boolean' }
        },
        required: ['query']
      }
    },
  • index.js:34-34 (registration)
    The TOOLS array (line 34) which holds all tool definitions including vybsly_knowledge (line 56-67). Registered via ListToolsRequestSchema handler on line 417.
    const TOOLS = [
  • Handler for the vybsly_knowledge tool in the CallToolRequestSchema switch statement. Calls the Vybsly API /knowledge endpoint with query, limit, strict, and research parameters.
    case 'vybsly_knowledge':
      result = await vybslyCall('/knowledge', {
        q: args.query,
        limit: args.limit || 10,
        ...(args.strict && { strict: 'true' }),
        ...(args.research && { research: 'true' })
      });
      break;
  • Description of vybsly_knowledge in the search-syntax resource guide: 'federated search across the web index AND the encyclopedia (Vybpedia) in one call.'
    - **vybsly_knowledge** — federated search across the web index AND the encyclopedia (Vybpedia) in one call.
  • Guidance in the search-syntax resource: entity/fact questions should use vybsly_knowledge.
    - **Entity/fact question** (e.g. "what is blockchain", "who is Einstein") → \`vybsly_knowledge\`
Behavior4/5

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

With no annotations, the description must disclose behavioral traits. It states the tool returns results tagged by source, which is a key behavioral detail. However, it does not mention any potential side effects, rate limits, or authentication needs, but for a read-only search tool, the provided information is sufficient.

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, front-loaded with the core purpose, and every sentence adds value. There is no fluff or redundancy.

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?

The description is adequate for a simple search tool but lacks detail on output structure (no output schema) and does not fully cover the parameters (50% coverage). The key differentiator (source tagging) is mentioned, but the return format is left implicit.

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

Parameters2/5

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

Schema description coverage is only 50% (two of four parameters lack descriptions: strict and research). The description adds no parameter-level meaning beyond what the schema already provides. It fails to clarify the role of the undocumented boolean parameters, which is a significant gap.

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 that the tool performs a federated search combining a web index and an encyclopedia, and that results are tagged by source. It distinguishes itself from sibling tools like vybsly_search and vybsly_news by specifying its best use case for factual questions needing both breadth and authority.

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 description provides clear guidance on when to use this tool: for 'factual questions needing both breadth (web) and authority (encyclopedia).' While it implies when not to use it (e.g., for simple web searches), it does not explicitly exclude alternatives or mention when to use sibling tools.

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/BlueFusionLab/vybsly-mcp'

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