Skip to main content
Glama
NoeCalle

OpenDSS MCP Server

by NoeCalle

evaluar_tiempo_despeje_p5d

Evaluates a device's clearing time for a given current and checks whether TOTAL_CLEARING_TIME stays within the allowed domain.

Instructions

Promueve a clearing time solo TOTAL_CLEARING_TIME dentro de dominio.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
current_aYes
dispositivoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not explain what the tool returns, whether it mutates state, what permissions are needed, how errors are handled, or what a 'promotion' result means. The phrase 'Promueve a clearing time' is unclear rather than informative.

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

Conciseness2/5

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

The description is a single short sentence, but it is under-specified and awkward rather than concise. It does not front-load a clear action or purpose, and its brevity does not help an agent understand the tool.

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?

With no annotations, no output schema, and two undocumented required parameters, the description is completely inadequate for an evaluation tool. An agent would need to infer almost everything from the tool name and surrounding context.

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?

The schema has two required parameters, 'dispositivo' and 'current_a', with 0% description coverage. The description does not mention either parameter or explain their expected format, units, or role in the evaluation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Promueve a clearing time solo TOTAL_CLEARING_TIME dentro de dominio,' which is vague and not a clear verb+resource statement. It loosely gestures at clearing time but does not clearly say the tool evaluates clearing time, nor does it distinguish itself from siblings like obtener_contrato_tiempo_despeje_p5d.

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?

There is no guidance on when to use this tool, when not to use it, or which sibling tool to use instead. The phrase 'dentro de dominio' is too vague to count as usage context.

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