Skip to main content
Glama
angrysky56

Advanced Reasoning MCP Server

list_system_json

Retrieve all available system JSON files with their names, domains, and descriptions to access structured data for enhanced reasoning and memory storage.

Instructions

List all available system JSON files.

Returns list of all system JSON files with their names, domains, and descriptions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler implementation in SystemJSON class that lists all system JSON files by reading the storage directory, parsing each JSON, and extracting name, domain, description. Sorts alphabetically and handles errors gracefully.
    async listSystemJSON(): Promise<{ files: Array<{ name: string; domain: string; description: string }> }> {
      try {
        const files = await fs.readdir(this.systemJsonPath);
        const systemFiles = [];
    
        for (const file of files) {
          if (file.endsWith('.json') && !file.endsWith('.tmp')) {
            try {
              const filePath = path.join(this.systemJsonPath, file);
              const jsonContent = await fs.readFile(filePath, 'utf-8');
              const data = JSON.parse(jsonContent) as SystemJSONData;
    
              systemFiles.push({
                name: data.name,
                domain: data.domain,
                description: data.description
              });
            } catch (error) {
              // Skip corrupted files
              console.error(`Skipping corrupted system JSON file: ${file}`, error);
            }
          }
        }
    
        return { files: systemFiles.sort((a, b) => a.name.localeCompare(b.name)) };
      } catch (error) {
        console.error('Failed to list system JSON files:', error);
        return { files: [] };
      }
    }
  • Tool handler wrapper in AdvancedReasoningServer that calls SystemJSON.listSystemJSON(), formats the result as MCP-standard content response, and handles errors.
    public async listSystemJSON(): Promise<{ content: Array<{ type: string; text: string }>; isError?: boolean }> {
      try {
        const result = await this.systemJson.listSystemJSON();
    
        return {
          content: [{
            type: "text",
            text: JSON.stringify({
              files: result.files,
              totalFiles: result.files.length,
              status: 'success'
            }, null, 2)
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: JSON.stringify({
              error: error instanceof Error ? error.message : String(error),
              status: 'failed'
            }, null, 2)
          }],
          isError: true
        };
      }
    }
  • src/index.ts:1452-1453 (registration)
    Dispatch registration in the CallToolRequestHandler switch statement that routes 'list_system_json' tool calls to the reasoningServer handler.
    case "list_system_json":
      return await reasoningServer.listSystemJSON();
  • Tool definition including name, description, and input schema (no required parameters).
    const LIST_SYSTEM_JSON_TOOL: Tool = {
      name: "list_system_json",
      description: `List all available system JSON files.
    
    Returns list of all system JSON files with their names, domains, and descriptions.`,
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    };
  • src/index.ts:1405-1405 (registration)
    Registration of the LIST_SYSTEM_JSON_TOOL in the tools array returned by ListToolsRequestHandler.
    LIST_SYSTEM_JSON_TOOL
Behavior3/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 discloses that the tool returns a list with specific fields (names, domains, descriptions), which is useful behavioral context. However, it lacks details on potential limitations like pagination, rate limits, or authentication requirements, leaving gaps in transparency.

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 concise sentences with zero waste: the first states the action and resource, and the second specifies the return format. It is front-loaded with the core purpose and efficiently structured, earning its place without redundancy.

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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is mostly complete for a list operation. It explains what is returned, but could improve by addressing potential behavioral aspects like ordering or completeness of the list. However, it adequately covers the core functionality without being overly complex.

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 tool has 0 parameters, and schema description coverage is 100% (though trivial since there are no parameters). The description does not need to add parameter semantics, so it meets the baseline of 4 for zero-parameter tools, as it appropriately focuses on output behavior instead.

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 specific action ('List all available') and resource ('system JSON files'), distinguishing it from siblings like 'get_system_json' (likely retrieves one file) and 'search_system_json' (likely filters results). It explicitly mentions what information is returned (names, domains, descriptions), making the purpose unambiguous.

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 implies usage when needing a comprehensive list of all system JSON files without filtering, as opposed to 'search_system_json' which likely allows filtering. However, it does not explicitly state when NOT to use this tool or name alternatives, missing full explicit guidance.

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/angrysky56/advanced-reasoning-mcp'

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