Skip to main content
Glama
angrysky56

Advanced Reasoning MCP Server

get_current_library_info

Retrieve details about the active memory library, including its name, node count, sessions, and metadata for enhanced reasoning workflows.

Instructions

Get information about the currently active memory library.

Shows current library name, number of nodes, sessions, and other metadata.

Returns current library information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function getCurrentLibraryInfo() in AdvancedReasoningServer class. Returns JSON with current library name and memory statistics.
    public getCurrentLibraryInfo(): { content: Array<{ type: string; text: string }>; isError?: boolean } {
      try {
        return {
          content: [{
            type: "text",
            text: JSON.stringify({
              currentLibrary: this.memory.getCurrentLibraryName(),
              memoryStats: this.memory.getMemoryStats(),
              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
        };
      }
    }
  • Tool schema definition for 'get_current_library_info' with empty input schema as it takes no parameters.
    const GET_LIBRARY_INFO_TOOL: Tool = {
      name: "get_current_library_info",
      description: `Get information about the currently active memory library.
    
    Shows current library name, number of nodes, sessions, and other metadata.
    
    Returns current library information.`,
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    };
  • src/index.ts:1395-1407 (registration)
    Registration of the tool in the ListToolsRequestSchema handler, including it in the tools list.
      tools: [
        ADVANCED_REASONING_TOOL,
        QUERY_MEMORY_TOOL,
        CREATE_LIBRARY_TOOL,
        LIST_LIBRARIES_TOOL,
        SWITCH_LIBRARY_TOOL,
        GET_LIBRARY_INFO_TOOL,
        CREATE_SYSTEM_JSON_TOOL,
        GET_SYSTEM_JSON_TOOL,
        SEARCH_SYSTEM_JSON_TOOL,
        LIST_SYSTEM_JSON_TOOL
      ],
    }));
  • src/index.ts:1431-1432 (registration)
    Dispatch/execution handler in the CallToolRequestSchema switch statement that calls the tool handler.
    case "get_current_library_info":
      return reasoningServer.getCurrentLibraryInfo();
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation ('Get information') but doesn't explicitly state if it's safe, requires permissions, has rate limits, or what happens if no library is active. The description adds some context about returned data but lacks critical behavioral details for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded, with the first sentence stating the core purpose. The second sentence adds useful details about returned data, and the third sentence is slightly redundant but not wasteful. Overall, it's well-structured and efficient, though minor trimming could improve it further.

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?

Given the tool's low complexity (0 parameters) and lack of annotations and output schema, the description is minimally adequate. It explains what the tool does and what data it returns, but it doesn't cover behavioral aspects like error handling or dependencies on an active library. For a simple tool, this is acceptable but leaves gaps in completeness.

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 zero parameters, and schema description coverage is 100%, so there's no need for parameter documentation in the description. The description appropriately doesn't discuss parameters, earning a high baseline score. It could be a 5 if it explicitly noted 'no parameters required,' but the current omission is acceptable.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Get information') and resource ('currently active memory library'), and it lists specific data returned (name, nodes, sessions, metadata). However, it doesn't explicitly differentiate from sibling tools like 'list_memory_libraries' or 'get_system_json', which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to prefer this over 'list_memory_libraries' (which might list all libraries) or 'get_system_json' (which might retrieve system data), nor does it specify prerequisites like requiring an active library. This leaves usage context unclear.

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