Load a pandapower grid to retrieve load summaries, total power, voltage levels, and load types. Optionally return the per-load table for detailed inspection.
Load a grid: summary of loads, total power, voltage levels and whether load types are known.
| Name | Required | Description | Default |
|---|---|---|---|
| grid | Yes | Built-in grid id, or a pandapower .json/.xlsx file (uploaded file name) | |
| include_loads | No | Also return the per-load table (large) |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears the full burden. It discloses the returned summary fields, which is useful since there is no output schema, but it does not state whether the operation is read-only, whether it caches or mutates state, or any performance/auth considerations.
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 front-loaded sentence with zero filler; the verb and returned content are stated immediately.
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?
With no output schema, the description helpfully names the summary contents, but it omits usage routing against sibling tools and any behavioral safety profile. For an agent needing to choose correctly among grid-related tools, these gaps matter.
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?
Schema description coverage is 100%, so the schema already documents both parameters (grid id/file and include_loads). The description adds no parameter semantics beyond the schema, warranting the baseline of 3.
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 ('Load') and resource ('grid'), and enumerates the returned summary: loads, total power, voltage levels, and load-type status. It does not differentiate itself from siblings like get_grid_loads or list_grids, so the agent must infer the boundary.
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 guidance on when to use this tool versus get_grid_loads, list_grids, or get_default_settings. The description only says what it does, leaving the agent to guess the appropriate context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.