Skip to main content
Glama
Sign In
mcp-solver

mcp-solver

by szeider
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

python_status

Check kernel state, including active kernels, defined variables, and installed packages. Pass an optional kernel ID to inspect a specific Python session.

Instructions

Check kernel state: active kernels, defined variables, packages.

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

Input Schema

NameRequiredDescriptionDefault
kernel_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Check' implies a read-only operation, but it does not explicitly state that it is non-destructive, nor does it describe side effects, authorization needs, or rate limits. It only lists what is inspected, which is minimal behavioral context.

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?

A single, front-loaded sentence with no filler. It efficiently conveys the core purpose in one clause.

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

Completeness3/5

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

For a simple no-required-parameter tool with no output schema, the description gives an outline of what is returned (kernels, variables, packages). However, it omits usage context and parameter semantics, leaving gaps an agent must infer.

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

Parameters2/5

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

The schema has 0% description coverage and the description never mentions the optional kernel_id parameter. It does not explain what the parameter does, when to supply it, or what the default behavior is when omitted.

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 specific verb 'Check' and resource 'kernel state', and enumerates the inspected items (active kernels, variables, packages). It is clear but does not differentiate this tool from siblings like python_exec or python_interrupt.

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 when-to-use guidance is given. The description does not say when to prefer this over python_exec or python_interrupt, nor does it state any prerequisites like requiring an active kernel.

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