From jkeenan at pobox.com  Thu Mar 26 12:22:15 2026
From: jkeenan at pobox.com (James E Keenan)
Date: Thu, 26 Mar 2026 15:22:15 -0400
Subject: [tpm] Meeting tonight?
Message-ID: <b062e95d-3bc7-40fc-9a3b-02454cc9bd74@pobox.com>

I just learned that Toronto Perlmongers is having Stevan Little speak at 
7:00 pm EDT.

Please post the event information to this list.  I've been subscribed 
for 25 years, but not having previously subscribed to your Luma thingee, 
I would have missed this completely!

Thank you very much.
Jim Keenan

From olaf at vilerichard.com  Thu Mar 26 12:38:57 2026
From: olaf at vilerichard.com (Olaf Alders)
Date: Thu, 26 Mar 2026 15:38:57 -0400
Subject: [tpm] Meeting tonight?
In-Reply-To: <b062e95d-3bc7-40fc-9a3b-02454cc9bd74@pobox.com>
References: <b062e95d-3bc7-40fc-9a3b-02454cc9bd74@pobox.com>
Message-ID: <d9f7940a-3a46-462f-8f18-561f7906471f@app.fastmail.com>

Hi Jim,

Tonight's meeting URL: https://luma.com/bdom1gut?tk=FkV6xL

Some of my messages to the list were not getting through. Let's see if this works.

Best,

Olaf

On Thu, Mar 26, 2026, at 3:22 PM, James E Keenan wrote:
> I just learned that Toronto Perlmongers is having Stevan Little speak at 
> 7:00 pm EDT.
> 
> Please post the event information to this list.  I've been subscribed 
> for 25 years, but not having previously subscribed to your Luma thingee, 
> I would have missed this completely!
> 
> Thank you very much.
> Jim Keenan
> _______________________________________________
> toronto-pm mailing list
> toronto-pm at pm.org
> https://mail.pm.org/mailman/listinfo/toronto-pm
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/toronto-pm/attachments/20260326/d170e721/attachment.html>

From marcperryster at gmail.com  Thu Mar 26 12:40:17 2026
From: marcperryster at gmail.com (Marc Perry)
Date: Thu, 26 Mar 2026 15:40:17 -0400
Subject: [tpm] Fwd:  Meeting tonight?
In-Reply-To: <CADuVt3TL3Qv-8+GaZ11f7yu-bg=z1agmyqMn2w-OxfZ-K_iN4A@mail.gmail.com>
References: <b062e95d-3bc7-40fc-9a3b-02454cc9bd74@pobox.com>
 <CADuVt3TL3Qv-8+GaZ11f7yu-bg=z1agmyqMn2w-OxfZ-K_iN4A@mail.gmail.com>
Message-ID: <CADuVt3QU1-J5EuXvCN+=Da1rO=KFsPAEk1wRdeYMP_8OtU0WqA@mail.gmail.com>

---------- 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>

From olaf at vilerichard.com  Sat Mar 28 05:10:18 2026
From: olaf at vilerichard.com (Olaf Alders)
Date: Sat, 28 Mar 2026 08:10:18 -0400
Subject: [tpm] Fwd:  Meeting tonight?
In-Reply-To: <CADuVt3QU1-J5EuXvCN+=Da1rO=KFsPAEk1wRdeYMP_8OtU0WqA@mail.gmail.com>
References: <b062e95d-3bc7-40fc-9a3b-02454cc9bd74@pobox.com>
 <CADuVt3TL3Qv-8+GaZ11f7yu-bg=z1agmyqMn2w-OxfZ-K_iN4A@mail.gmail.com>
 <CADuVt3QU1-J5EuXvCN+=Da1rO=KFsPAEk1wRdeYMP_8OtU0WqA@mail.gmail.com>
Message-ID: <c3c87144-b382-4dbc-b5bd-e2f8ad75bbf5@app.fastmail.com>

On a related note, some of us will informally be chatting about AI. https://luma.com/dphtpj7m

Anyone is welcome to join. No expertise required. 

On Thu, Mar 26, 2026, at 3:40 PM, Marc Perry wrote:
> 
> 
> ---------- 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
> 
> 
>> 
> _______________________________________________
> toronto-pm mailing list
> toronto-pm at pm.org
> https://mail.pm.org/mailman/listinfo/toronto-pm
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/toronto-pm/attachments/20260328/48bd2f64/attachment.html>