Skip to main content
Glama
ahmad2x4

Seq MCP Server

by ahmad2x4

get-alertstate

Retrieve the current alert state from Seq to monitor system status and identify active issues requiring attention.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get-alertstate' tool. It makes a request to the SEQ API endpoint '/api/alertstate' using the makeSeqRequest helper, formats the response as JSON text, and handles errors by returning an error message.
      async () => {
        try {
          const alertState = await makeSeqRequest<any>('/api/alertstate');
          
          return {
            content: [{
              type: "text",
              text: JSON.stringify(alertState, null, 2)
            }]
          };
        } catch (error) {
          const err = error as Error;
          return {
            content: [{
              type: "text",
              text: `Error fetching alert state: ${err.message}`
            }],
            isError: true
          };
        }
      }
    );
  • Registers the 'get-alertstate' tool with the MCP server, including empty input schema and inline handler function.
    server.tool(
      "get-alertstate",
      {},
      async () => {
        try {
          const alertState = await makeSeqRequest<any>('/api/alertstate');
          
          return {
            content: [{
              type: "text",
              text: JSON.stringify(alertState, null, 2)
            }]
          };
        } catch (error) {
          const err = error as Error;
          return {
            content: [{
              type: "text",
              text: `Error fetching alert state: ${err.message}`
            }],
            isError: true
          };
        }
      }
    );
  • Empty Zod schema object indicating the tool takes no input parameters.
    {},
  • Helper function used by the handler to make authenticated HTTP requests to the SEQ API, constructing the URL with API key and parameters, handling fetch and JSON parsing with error checking.
    async function makeSeqRequest<T>(endpoint: string, params: Record<string, string> = {}): Promise<T> {
      const url = new URL(`${SEQ_BASE_URL}${endpoint}`);
      
      // Add API key as query parameter
      url.searchParams.append('apiKey', SEQ_API_KEY);
      
      // Add additional query parameters
      Object.entries(params).forEach(([key, value]) => {
        if (value !== undefined && value !== null) {
          url.searchParams.append(key, value);
        }
      });
    
      const headers: Record<string, string> = {
        'Accept': 'application/json',
        'X-Seq-ApiKey': SEQ_API_KEY
      };
    
      const response = await fetch(url.toString(), { headers });
    
      if (!response.ok) {
        throw new Error(`SEQ API error: ${response.statusText} (${response.status})`);
      }
    
      return response.json();
    }
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/ahmad2x4/mcp-server-seq'

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