Skip to main content
Glama
mumez

pharo-smalltalk-interop-mcp-server

export_package

Export a Smalltalk package to Tonel format at a specified file path. Provide package name and optional output directory.

Instructions

Export a package in Tonel format.

Args: package_name: The name of the package to export path: The path where to export the package (default: /tmp)

Returns: dict: API response with success/error and result - Success: {"success": True, "result": str} - result contains export success message with path - Error: {"success": False, "error": str} - error contains error message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
package_nameYesThe name of the package to export
pathNoThe path where to export the package/tmp

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

The description explains the return format but omits behavioral traits such as side effects (file creation), permissions needed, or error conditions beyond a generic error dict.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description follows a clear docstring structure with Args and Returns sections, front-loading the purpose. It is concise but could be more succinct.

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?

Covers return values adequately with the output schema-like dict. However, lacks usage context and behavioral details, making it incomplete for a tool with no annotations.

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?

Schema coverage is 100%. The description adds the default path value but otherwise restates parameter names. Baseline score of 3 is appropriate.

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 the action ('Export a package') and the format ('Tonel format'), distinguishing it from sibling 'import_package'.

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 explicit guidance on when to use this tool versus alternatives. No context about prerequisites or conditions for exporting.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mumez/pharo-smalltalk-interop-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server