Skip to main content
Use doctor commands and targeted logs when tools fail to import or execute.
The user runs praisonai tools doctor, fixes dependencies, and retries the agent call.

How It Works


How to Use Tools Doctor

praisonai tools doctor now walks the full ToolResolver chain — local tools.py, wrapper ToolRegistry, praisonaiagents.tools, praisonai-tools, and entry-point plugins. As of PR #2642, a tool that resolves at run time is guaranteed to appear here, so the doctor no longer reports false “missing” results for registered or plugin tools.
1

Run Tools Doctor

2

Check Specific Tool

3

Review Diagnostics

Doctor output shows:
  • Tool availability
  • Missing dependencies
  • Configuration issues
  • Import errors
4

Fix Identified Issues

Install missing packages or fix configuration based on doctor output.

How to Debug Tool Resolution

1

Resolve Tool Name

2

Check Tool Sources

3

Discover Available Tools

4

Search for Tools

How to Debug Tools with Python

1

Test Tool Directly

2

Check Tool Signature

3

Validate Docstring

4

Test with Agent

How to Debug Tool Registry

1

Create Registry

2

List All Tools

3

Check Specific Tool

Common Tool Issues

Debug CLI Commands

Best Practices

The doctor walks the whole resolver chain, so it distinguishes a missing dependency from a genuinely unregistered tool in one command.
Call the function directly and check its return type before blaming the agent — most failures are plain Python errors.
Use inspect.signature to confirm the tool exposes the parameters and return type the model expects.

Create Custom Tools

Build tools with correct signatures

Assign Tools to Templates

Wire tools into recipes