Runs OpenDSS power-flow calculations and updates the detailed view so users can inspect voltages, currents, and losses in distribution networks.
Resuelve flujo con OpenDSS y actualiza la vista detallada.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It implies a compute-plus-write behavior ('actualiza la vista detallada') but never states prerequisites (a configured circuito/workspace), whether results are cached or overwritten, or whether the underlying state is mutated destructively.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single compact sentence with no filler and the computation front-loaded ahead of the side effect. It is efficient, though the second clause is under-specified rather than merely brief.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a heavy simulation tool with no output schema and no annotations, the description says almost nothing about what the run produces, how the agent retrieves results, or what 'vista detallada' means. An agent could invoke it but would not know what to expect or do next.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 of 4 applies. No parameter-level detail is missing.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Resuelve flujo') plus the engine used ('con OpenDSS'), which distinguishes it from the sibling ejecutar_flujo_pandapower. The trailing clause 'actualiza la vista detallada' hints at a side effect but is vague about what view is updated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No statement of when to pick this over ejecutar_flujo_pandapower or analizar_flujo_operacion. The engine name is the only implicit differentiator, leaving the agent to infer the selection condition.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.