Skip to main content
Glama
Sign In
iec-mcp

iec-mcp

by tadnir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

iec_session_status

Check if the server is signed in to IEC, view session start and expiry times, and get the sign-in link when authentication is missing.

Instructions

Whether this server is signed in to IEC, since when, until when, and the sign-in link when it is not.

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": "iec_session_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden, and it does disclose the condition-dependent return content (the sign-in link only appears when the session is not active). The interrogative framing also makes the read-only nature evident. It stops short of stating explicitly that there are no side effects or whether the link expires.

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?

A single front-loaded sentence that covers all four reported facts with no filler or repetition. Nothing could be removed without losing information.

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 status query with no output schema, the description supplies the return fields an agent needs (state, since, until, sign-in link). A brief pointer to iec_login for actually signing in would close the remaining gap.

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 takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies for a parameterless tool.

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 names a specific resource (this server's IEC session) and enumerates exactly what is reported: signed-in state, start time, expiry, and the sign-in link when inactive. That is enough to tell it apart from the mutating siblings iec_login and iec_logout, though it never names an alternative explicitly.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. An agent must infer on its own that this should be called before iec_login to decide whether authentication is needed; the description neither states that flow nor excludes any case.

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