Skip to main content
Glama
0xjcf
by 0xjcf

create-session

Initialize a new code analysis session to track and manage syntax analysis, dependency visualization, and AI-assisted development workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNoOptional description for this session

Implementation Reference

  • Handler function for the 'create-session' tool. Creates a new session using getSession(), retrieves the session ID, constructs a success response with session details, or returns an error response if an exception occurs.
      async ({ description }) => {
        try {
          const session = getSession();
          const sessionId = session.getSessionId();
    
          const result = createSuccessResponse(
            { sessionId, description, created: new Date().toISOString() },
            "create-session"
          );
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result, null, 2),
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(
                  createErrorResponse(
                    error instanceof Error ? error.message : String(error),
                    "create-session"
                  ),
                  null,
                  2
                ),
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Input schema definition for the 'create-session' tool, specifying an optional 'description' parameter as a string.
    {
      description: z
        .string()
        .optional()
        .describe("Optional description for this session"),
  • Registers the 'create-session' tool on the MCP server instance using server.tool(), including schema and handler function.
    server.tool(
      "create-session",
      {
        description: z
          .string()
          .optional()
          .describe("Optional description for this session"),
      },
      async ({ description }) => {
        try {
          const session = getSession();
          const sessionId = session.getSessionId();
    
          const result = createSuccessResponse(
            { sessionId, description, created: new Date().toISOString() },
            "create-session"
          );
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result, null, 2),
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(
                  createErrorResponse(
                    error instanceof Error ? error.message : String(error),
                    "create-session"
                  ),
                  null,
                  2
                ),
              },
            ],
            isError: true,
          };
        }
      }
    );
  • src/server.ts:84-85 (registration)
    Registers the session manager feature (including create-session tool) by calling registerSessionTools via registerToolsOnce in the main server setup.
    console.log("• Registering session manager features...");
    registerToolsOnce(registerSessionTools);
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/0xjcf/MCP_CodeAnalysis'

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