Skip to main content
Glama

estado_conexion

Read-only

Determines whether the local browser session is open and if Teams needs authentication before you query courses, assignments, or announcements.

Instructions

Comprueba si el navegador está abierto y si Teams requiere autenticación.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the two concrete facts being probed (browser state and Teams auth requirement), but it says nothing about latency, side effects, or how results are reported; with an output schema present, that is acceptable.

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

Conciseness4/5

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

It is a single short sentence with the checked conditions front-loaded and no filler. It is appropriately sized for a zero-parameter status tool, though it could have included one routing clause at little cost.

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?

An output schema exists, so return-value semantics need not be explained, and the annotations carry the safety profile. For a zero-parameter read-only status check, the definition is nearly complete; only the next-step guidance (what to do if authentication is required) is missing.

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. The baseline score of 4 applies because the schema cannot contain meaningful parameter semantics in this case.

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 uses a concrete verb ("Comprueba") and names exactly what is being checked: whether the browser is open and whether Teams requires authentication. This makes its role as a status probe clear and separates it from action-oriented siblings like iniciar_sesion, although it does not explicitly name any of them.

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?

The description never states when to call this tool versus alternatives, such as the condition or order for checking status before calling iniciar_sesion. The usage is only loosely inferable from the word "Comprueba", with no explicit context or exclusion criteria.

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