Skip to main content
Glama

authstatus

Check if you're logged into eClass to access course materials and perform platform operations.

Instructions

Check authentication status with eClass

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
random_stringYesDummy parameter for no-parameter tools

Implementation Reference

  • The main handler function for the 'authstatus' tool, which calls the authentication helper to generate the response.
    async def handle_authstatus() -> List[types.TextContent]:
        """Handle checking authentication status."""
        return [authentication.format_authstatus_response(session_state)]
  • Registration of the 'authstatus' tool in the @server.list_tools() handler, defining its name, description, and input schema.
    types.Tool(
        name="authstatus",
        description="Check authentication status with eClass",
        inputSchema={
            "type": "object",
            "properties": {
                "random_string": {
                    "type": "string",
                    "description": "Dummy parameter for no-parameter tools"
                },
            },
            "required": ["random_string"],
        },
    ),
  • Input schema for the 'authstatus' tool, which uses a dummy 'random_string' parameter since the tool takes no real inputs.
    inputSchema={
        "type": "object",
        "properties": {
            "random_string": {
                "type": "string",
                "description": "Dummy parameter for no-parameter tools"
            },
        },
        "required": ["random_string"],
    },
  • Helper function that generates the formatted text response for authentication status based on the session state.
    def format_authstatus_response(session_state: SessionState) -> types.TextContent:
        """Format authentication status response for MCP."""
        if not session_state.logged_in:
            return types.TextContent(
                type="text",
                text="Status: Not logged in",
            )
        
        if session_state.is_session_valid():
            return types.TextContent(
                type="text",
                text=f"Status: Logged in as {session_state.username}\nCourses: {len(session_state.courses)} enrolled",
            )
        
        return types.TextContent(
            type="text",
            text="Status: Session expired. Please log in again.",
        )
Behavior2/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 only states the purpose without disclosing behavioral traits such as whether it requires authentication, what the response format is, or any rate limits. For a tool with zero annotation coverage, this is inadequate.

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 a single, clear sentence with no wasted words. It's appropriately sized and front-loaded, making it easy to understand immediately.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., success/failure, user details) or any behavioral context, which is necessary for an authentication-related tool with no structured data support.

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 schema description coverage is 100%, so the schema fully documents the single parameter. The description doesn't add any parameter information, which is acceptable since the schema handles it. With 0 parameters of real semantic weight (the parameter is a dummy), a baseline of 4 is appropriate.

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 as 'Check authentication status with eClass', which is a specific verb ('Check') and resource ('authentication status') combination. It doesn't explicitly distinguish from siblings like 'login' or 'logout', but the purpose is unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives like 'login' or 'logout'. The description states what it does but offers no context about when it should be invoked or what scenarios it addresses.

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/sdi2200262/eclass-mcp-server'

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