Skip to main content
Glama
Sign In
ipython-mcp

ipython-mcp

by husams
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

reload

Refresh explicitly named imported modules in a running IPython session and update their bindings to apply code changes without restarting.

Instructions

Reload explicitly named imported modules and refresh their bindings.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "modules": "<modules>"
    },
    "name": "reload"
  }
}

Input Schema

NameRequiredDescriptionDefault
modulesYes

Output Schema

NameRequiredDescriptionDefault
errorNo
resultsYes
runtimeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It mentions refreshing bindings but does not disclose potential side effects, whether the operation is safe, required permissions, or impact on dependent modules.

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?

The description is a single, front-loaded sentence with no wasted words. It states the action and object clearly, earning full credit for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even with an output schema, the description omits crucial contextual details for a dynamic reload operation, such as when it should be used, what side effects occur, and how it interacts with the runtime environment. The sparse description is inadequate for a tool that likely modifies execution state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning to the 'modules' parameter by describing it as 'explicitly named imported modules', which clarifies the input format as a list of module names. However, with 0% schema coverage, it leaves gaps such as how module names should be formatted and error behavior.

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

Purpose5/5

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

The description clearly states a specific action (reload) on a specific resource (imported modules) and adds the qualifier 'explicitly named' to indicate scope. This distinguishes it from generic operations like execute or list.

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?

No guidance is provided on when to use this tool versus alternatives such as reset or execute. There is no mention of prerequisites, exclusions, or typical use cases beyond the basic action.

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