Skip to main content
Glama

map_network

Explore the entire knowledge network organized by category. Returns all categories with module counts, top modules per category, and total statistics. Discover what knowledge is available and get an overview of the knowledge base.

Instructions

Browse the entire Celiums knowledge network organized by category. Returns all categories with module counts, top modules per category, and total statistics. Use to explore what knowledge is available, discover categories, or get an overview of the knowledge base. Behavior: queries the module index, groups by category, returns a structured map with counts. No parameters needed — returns the full network overview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Primary handler (OpenCore MCP): retrieves the module store index and returns it as JSON. This is the most minimal handler – it just delegates to store.getIndex().
    const handleMapNetwork: McpToolHandler = async (_args, ctx) => {
      const store = getModuleStore(ctx);
      const idx = await store.getIndex();
      return okJson(idx);
    };
  • Secondary handler (ToolRegistry): browses knowledge network by category. Supports optional domain filter. If domain given, returns modules in that category; otherwise returns all categories with module counts.
    private async handleMapNetwork(args: Record<string, unknown>): Promise<ToolResult> {
      const domain = args.domain as string | undefined;
      const index = await this.store.getIndex();
    
      if (domain) {
        const count = index.categories[domain] ?? 0;
        if (count === 0) {
          return this.textResult(`No modules found in category "${domain}".`);
        }
        const modules = await this.store.getByCategory(domain);
        const list = modules.map((m) => `- **${m.name}** — ${m.description?.slice(0, 80) || ""}`).join("\n");
        return this.textResult(`**${domain}** (${count} modules):\n\n${list}`);
      }
    
      const categories = Object.entries(index.categories)
        .sort(([, a], [, b]) => b - a)
        .map(([cat, count]) => `- **${cat}**: ${count} modules`)
        .join("\n");
    
      return this.textResult(
        `**Celiums Knowledge Network** — ${index.totalModules.toLocaleString()} modules\n\n${categories}`
      );
    }
  • Registration and schema for map_network in ToolRegistry (knowledge package). Takes optional 'domain' string parameter.
    this.register({
      name: "map_network",
      description: "Browse all available modules organized by category. Discover what knowledge domains are available.",
      inputSchema: {
        type: "object",
        properties: {
          domain: { type: "string", description: "Filter by specific domain/category (optional)" },
        },
      },
      requiresInference: false,
      category: "discovery",
    }, this.handleMapNetwork.bind(this));
  • Registration and schema for map_network in the OpenCore MCP tools array. No input parameters required; returns full network overview as JSON.
    {
      group: 'opencore',
      definition: {
        name: 'map_network',
        description: 'Browse the entire Celiums knowledge network organized by category. Returns all categories with module counts, top modules per category, and total statistics. Use to explore what knowledge is available, discover categories, or get an overview of the knowledge base. Behavior: queries the module index, groups by category, returns a structured map with counts. No parameters needed — returns the full network overview.',
        inputSchema: { type: 'object', properties: {} },
      },
      handler: handleMapNetwork,
    },
  • Dashboard server-side helper that calls the map_network MCP tool via mcpCall, optionally passing a category filter.
    export async function mapNetwork(category?: string) {
      return mcpCall('map_network', category ? { category } : {});
    }
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It explains the internal behavior: 'queries the module index, groups by category, returns a structured map with counts.' It also notes that no parameters are needed and that it returns the full overview, fully disclosing the tool's operation.

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 concise with four sentences: purpose, content, usage, and behavior/parameter note. Information is front-loaded and every sentence adds value without redundancy.

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

Completeness5/5

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

Given zero parameters and no output schema, the description fully explains what the tool returns (categories, counts, top modules, total stats) and how it works (queries index, groups by category). This is complete for its complexity level.

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, and the description explicitly confirms 'No parameters needed.' With 100% schema coverage, the description adds no extra meaning but is consistent. Baseline for 0 params is 4.

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 action: 'Browse the entire Celiums knowledge network organized by category.' It specifies the output content (categories, module counts, top modules, total statistics) and distinguishes from sibling tools by focusing on network overview rather than individual records or actions.

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?

Explicit usage guidance is provided: 'Use to explore what knowledge is available, discover categories, or get an overview of the knowledge base.' While no explicit when-not or alternatives are given, the sibling tools have clearly different purposes, making this sufficient.

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/terrizoaguimor/celiums-memory'

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