flowchart TD
%% Nodes
UserMessage("User Message")
Clasification("Classification")
ContextFound{"Context Found"}
NoContextInferece("No Context Inference")
ContextHasRequirements{"Context Has Requirements"}
AddNoContextSystemMessage("Add No Context System Message")
AddEmptyContextSystemMessate("Add Empty Context System Message")
AllContextFieldsFilled{"All Context Fields Filled"}
ContextHasAction{"Context Has Action"}
ExtractRequirementsFromConversation("Extract Requirements From Conversation")
CheckForAllContextFilledAfterExtraction{"Check for All Context Filled After Extraction"}
GenerateConfirmationMessage("Generate Confirmation Message")
ContextNeedsConfirmation{"Context Needs Confirmation"}
AskForRequirements("Ask for Requirements")
UserMessageIsConfirmationMessage{"User Message is Confirmation Message"}
ExecuteContextAction("Execute Context Action")
AddSystemMessageBasedOnResponsePayload("Add System Message Based On Payload Response")
CleanMemoryAndFinalizeContext("Clean Memory And Finalize Context")
%% Edge connections between nodes
UserMessage --> Clasification --> ContextFound
ContextFound -->|No | NoContextInferece
NoContextInferece --> AddNoContextSystemMessage
ContextFound -->|Yes | ContextHasRequirements
ContextHasRequirements -->|Yes | AllContextFieldsFilled
AllContextFieldsFilled --> |No | ExtractRequirementsFromConversation --> CheckForAllContextFilledAfterExtraction --> |No | AskForRequirements
AllContextFieldsFilled -->|Yes | ContextNeedsConfirmation
CheckForAllContextFilledAfterExtraction -->|Yes | ContextNeedsConfirmation
ContextNeedsConfirmation --> |Yes | UserMessageIsConfirmationMessage --> |No | GenerateConfirmationMessage
UserMessageIsConfirmationMessage --> |Yes | ContextHasAction --> |Yes | ExecuteContextAction --> AddSystemMessageBasedOnResponsePayload --> CleanMemoryAndFinalizeContext
ContextHasAction --> |No | AddEmptyContextSystemMessate
ContextHasRequirements -->|No | ContextHasAction
%% Node Styling
style UserMessage fill:#0000FF, stroke:#FF5722, color:#FFFFFF
style AddNoContextSystemMessage fill:#FF5722, stroke:#FF5722, color:#FFFFFF
style AskForRequirements fill:#FF5722, stroke:#FF5722, color:#FFFFFF
style GenerateConfirmationMessage fill:#FF5722, stroke:#FF5722, color:#FFFFFF
style CleanMemoryAndFinalizeContext fill:#FF5722, stroke:#FF5722, color:#FFFFFF
style AddEmptyContextSystemMessate fill:#FF5722, stroke:#FF5722, color:#FFFFFF
Metadata
Release files for leonbonetti.fast-mcp 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| leonbonetti_fast_mcp-0.1.1.tar.gz | 9.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| leonbonetti_fast_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.5 kB
Release files / leonbonetti_fast_mcp-0.1.1.tar.gz
| Download URL | leonbonetti_fast_mcp-0.1.1.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
86b3777a0bf0768b541866b6ce679d12d2f50d8c6b12929b60a9725506ffac83
|
|
BLAKE2b-256 checksum How to use checksums |
32e8673e38784a9c5138267a86e293642e1659819832a0815b926b7732e43a13
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.13
|
Release files / leonbonetti_fast_mcp-0.1.1-py3-none-any.whl
| Download URL | leonbonetti_fast_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 11.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a8a207517b501f19883c67f5b8d1a02b53745412ba9175c59fb6691055c54c3f
|
|
BLAKE2b-256 checksum How to use checksums |
b0aef551fb0107640412e983935c4ea4047f309bbca0137f0f5c31281989b364
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.13
|
Security for leonbonetti.fast-mcp 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.