Skip to main content
Glama
Sign In
Aula MCP Server

Aula MCP Server

by ilenhart
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

aula_check_auth

Check if MitID QR code authentication completed after login. Retrieve a refreshed QR code if the previous one expired.

Instructions

Check if the MitID QR code was scanned and authentication completed. Call this after aula_login. May return a refreshed QR screenshot if the previous one expired.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "aula_check_auth"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It adds valuable behavioral context, such as the possibility of receiving a refreshed QR screenshot if the previous one expired. This is beyond the empty schema and gives the agent useful expectations.

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?

Two concise sentences, front-loaded with the core purpose. Every word earns its place; no filler or 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?

For a zero-parameter, no-output-schema tool, the description covers the essential context: what it does, when to call it, and a possible edge-case output. It could mention the exact return format, but this is not critical for a simple status check.

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, so there is nothing for the description to explain. The baseline of 4 applies, and the description appropriately focuses on behavior rather than parameters.

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 function: checking if MitID QR code scan and authentication completed. It uses a specific verb ('check') and resource, but it does not explicitly distinguish this from the sibling tool 'aula_session_status'.

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?

Explicitly instructs to call after 'aula_login', providing clear timing context. It does not mention alternatives or when not to use, but the 'after login' guideline is practical and direct.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools