[tpm] Fwd: Meeting tonight?

[Marc Perry]

---------- Forwarded message ---------
From: Marc Perry <marcperryster at gmail.com>
Date: Thu, Mar 26, 2026 at 3:26 PM
Subject: Re: [tpm] Meeting tonight?
To: James E Keenan <jkeenan at pobox.com>


https://luma.com/bdom1gut?tk=gG6BLS

Topic: Toronto.pm <http://toronto.pm/> - Lembark talk
    Time: Mar 26, 2026 07:00 PM Eastern Time (US and Canada)

https://us02web.zoom.us/j/83060065332?pwd=5caWQ49cB9yr4VCRseNWNEoVFmHCoo.1
    Meeting ID: 830 6006 5332       Passcode: 670376

Designing Perly MCPs for Claude
The MCP standard allows defining actions for cases where the AI doesn’t
already know how to glue
together shell commands or must make connections to specialized services
like databases. From the AI
and user’s point of view this MCP is defined by its tool specification.
This tells the AI when and how to
use the specific tools. Proper tool definition is critical to the proper
selection and use of the tools.
As a trivial example we start with a time service based on enums to specify
strftime formats for stan-
dard uses, descriptions to Claude on how to select and apply them. These
could obviously be supplied
by the date(1) shell command, but the focus here is on making effective
tool definitions and supporting
code and this is a suitably simple example. The next section describes
approaches to configuring the
tool, showing basic descriptions and how to extend each of them for better
accuracy in Claude’s calling
them. Following that will be examples of the data structures used by Claude
to call the MCP and Perl
code for handling them effectively. The result is a small, efficient,
lightweight module and executable
for generic MCP handling. The final sections describe extending the MCP to
handle arguments and


>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/toronto-pm/attachments/20260326/83ba2c07/attachment-0001.html>