algen-agent-tools 0.1.0a1__tar.gz

algen_agent_tools-0.1.0a1/.gitignore

@@ -0,0 +1,14 @@
+.venv/
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+coverage.xml
+htmlcov/
+dist/
+build/
+*.egg-info/
+.env
+.DS_Store

algen_agent_tools-0.1.0a1/CHANGELOG.md

@@ -0,0 +1,64 @@
+# Changelog
+
+All notable changes to Algen Agent Tools are recorded here. The project follows
+[Semantic Versioning](https://semver.org/); during the `0.x` series public contracts are
+experimental, and every breaking change carries an upgrade note.
+
+A tool's name, input schema, side effect and permission are part of the public contract.
+
+## [Unreleased]
+
+## [0.1.0a1] - 2026-10-27
+
+### Added
+
+- The package: `algen-agent-tools`, importable as `algen_agent_tools`, supporting
+  `algen-agent-runtime>=0.1.0a11,<0.2`. Each connector is a Runtime `Toolkit` registered by a
+  plugin in the `algen_agent_runtime.plugins` entry point group under the trusted prefix
+  `algen_agent_tools`, with one optional extra per connector and an `all` extra.
+- `algen_agent_tools.sample`: a dependency-free reference toolkit (`sample.echo`) used to check
+  an install end to end and as the template for new connectors.
+- PostgreSQL (`algen_agent_tools.postgres`, extra `postgres`): `PostgresToolkit.query` declares
+  a named, parameterised query as a typed tool, so the model never writes SQL. Reads run in a
+  read-only transaction and stream through a cursor that fails past a row limit; every
+  statement runs under a `statement_timeout` equal to the tool's timeout; writes can bind the
+  call's idempotency key for exactly-once SQL; unknown input fields are refused.
+  `fetch_rows` serves custom read tools. The plugin registers `postgres.list_tables` and
+  `postgres.describe_table`, limited to the configured schemas. `FakePostgres` for tests.
+- SMTP (`algen_agent_tools.smtp`) and Gmail (`algen_agent_tools.gmail`): `smtp.send_email`,
+  `gmail.send_email` (external, keyed, one attempt) and `gmail.list_messages` (read). The sender
+  is fixed by the deployment, the model cannot add headers, an optional domain allowlist bounds
+  recipients and Reply-To, and attachments are offered only with an artifact loader that receives
+  the call's `ToolContext` to check the artifact's tenant. The transports
+  (`SmtpEmailSender`, `GmailMailboxClient`) and message models (`algen_agent_tools.mail`) move
+  from `algen_agent_runtime.communications`, with one fix: the Gmail transport now delivers Bcc
+  recipients (it put no Bcc header in the raw message, so Gmail never sent to them). `FakeMailbox` for tests. An agent that
+  sends email leaves the `pii` guardrail out of `guardrail_policy.tool_policies`; with it, the
+  Runtime refuses the redacted arguments (documented on each connector page).
+- MCP governance overlays (`algen_agent_tools.mcp`, extra `mcp`): `McpOverlay` declares, per
+  remote tool, its side effect, approval rule, timeout, permissions, result limit and the input
+  schema it was reviewed against. Each declared tool is an ordinary Runtime tool, so `describe`
+  and Studio list it before anything connects; undeclared tools are never exposed; arguments are
+  validated against the closed schema; a tool the server dropped or whose schema changed is
+  refused (`on_drift: allow` relaxes this); stdio environment values must be `env://`
+  references; HTTP transports reach only the server's host. `overlay_plugin` declares an
+  overlay file from a project's plugin, `python -m algen_agent_tools.mcp snapshot` drafts one
+  from a live server for review, and `FakeMcpServer` serves tests.
+- `docs/migrating-from-runtime.md` maps the Runtime's deprecated `communications` connectors
+  and `database_tool` to this package.
+- `algen_agent_tools.testing`: `assert_toolkit_contract` and `toolkit_contract_problems` (the
+  Runtime's tool contract plus naming, permission-prefix and no-passthrough rules),
+  `describe_plugin` and `plugin_tools` (the Runtime inventory for one plugin, without calling a
+  tool).
+- An end-to-end test runs an agent through the Runtime's executor, guardrails and approval
+  flow: the email is sent once after approval and never after rejection.
+- CI: a PostgreSQL service-container job runs the integration tests; live email tests run only
+  with `ALGEN_TOOLS_LIVE=1`.
+- CI: lint, strict typing and tests on Python 3.12 and 3.13; the suite against the lowest and
+  highest supported Runtime; coverage; package build and a clean-install check that describes
+  every installed plugin; DCO, CodeQL, pip-audit, Bandit, Gitleaks and dependency review.
+- Brand assets (`docs/assets/brand`): the Tools logo and light and dark README banners in the
+  Algen palette, and `docs/releasing.md`.
+- Project policies: connector entry criteria, security review checklist, versioning and
+  deprecation policy (`docs/connector-policy.md`), contributor and agent guides, security policy
+  and governance.

algen_agent_tools-0.1.0a1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

algen_agent_tools-0.1.0a1/NOTICE

@@ -0,0 +1,8 @@
+Algen Agent Tools
+Copyright AlgenAI
+
+This product is built on Algen Agent Runtime (Apache-2.0).
+
+Connector names identify third-party services and protocols. Those names are trademarks of their
+respective owners; their use does not imply endorsement. Third-party dependencies retain their
+respective copyright and license terms.

algen_agent_tools-0.1.0a1/PKG-INFO

@@ -0,0 +1,197 @@
+Metadata-Version: 2.5
+Name: algen-agent-tools
+Version: 0.1.0a1
+Summary: Curated, governed connectors for Algen Agent Runtime agents
+Project-URL: Homepage, https://github.com/AlgenAI/algen-agent-tools
+Project-URL: Source, https://github.com/AlgenAI/algen-agent-tools
+Project-URL: Documentation, https://github.com/AlgenAI/algen-agent-tools#readme
+Project-URL: Issues, https://github.com/AlgenAI/algen-agent-tools/issues
+Project-URL: Changelog, https://github.com/AlgenAI/algen-agent-tools/blob/main/CHANGELOG.md
+Author: AlgenAI
+Maintainer: AlgenAI
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: agent-tools,agents,ai-governance,connectors,llm,mcp
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Software Development :: Libraries
+Classifier: Typing :: Typed
+Requires-Python: >=3.12
+Requires-Dist: algen-agent-runtime<0.2,>=0.1.0a11
+Provides-Extra: all
+Requires-Dist: algen-agent-runtime[mcp]<0.2,>=0.1.0a11; extra == 'all'
+Requires-Dist: asyncpg<1,>=0.29; extra == 'all'
+Provides-Extra: dev
+Requires-Dist: mypy<2,>=1.11; extra == 'dev'
+Requires-Dist: pytest-asyncio<2,>=1.3; extra == 'dev'
+Requires-Dist: pytest-cov<7,>=5; extra == 'dev'
+Requires-Dist: pytest<10,>=9.0.3; extra == 'dev'
+Requires-Dist: ruff<1,>=0.6; extra == 'dev'
+Provides-Extra: gmail
+Provides-Extra: mcp
+Requires-Dist: algen-agent-runtime[mcp]<0.2,>=0.1.0a11; extra == 'mcp'
+Provides-Extra: postgres
+Requires-Dist: asyncpg<1,>=0.29; extra == 'postgres'
+Provides-Extra: smtp
+Description-Content-Type: text/markdown
+
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/AlgenAI/algen-agent-tools/refs/heads/main/docs/assets/brand/banner-dark.svg">
+  <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/AlgenAI/algen-agent-tools/refs/heads/main/docs/assets/brand/banner-light.svg">
+  <img alt="Algen Agent Tools — Typed tools for agents. Governed by default." src="https://raw.githubusercontent.com/AlgenAI/algen-agent-tools/refs/heads/main/docs/assets/brand/banner-light.svg">
+</picture>
+
+# Algen Agent Tools
+
+[![Quality](https://github.com/AlgenAI/algen-agent-tools/actions/workflows/quality.yml/badge.svg)](https://github.com/AlgenAI/algen-agent-tools/actions/workflows/quality.yml)
+[![Security](https://github.com/AlgenAI/algen-agent-tools/actions/workflows/security.yml/badge.svg)](https://github.com/AlgenAI/algen-agent-tools/actions/workflows/security.yml)
+[![PyPI](https://img.shields.io/pypi/v/algen-agent-tools.svg)](https://pypi.org/project/algen-agent-tools/)
+[![Python 3.12+](https://img.shields.io/badge/python-3.12%2B-blue.svg)](https://www.python.org/downloads/)
+[![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+
+Curated, governed connectors for agents built on
+[Algen Agent Runtime](https://github.com/AlgenAI/algen-agent-runtime).
+
+Each connector is a Runtime `Toolkit` of narrow, typed actions, registered through a declared
+plugin. An agent names the plugin in `agent.yaml`, the Runtime checks every tool it enables, and
+Algen Agent Studio lists each tool with its side effect, permissions and environment variables
+from `algen-agent-runtime describe`, without running project code.
+
+> [!IMPORTANT]
+> `0.1.0a1` is a pre-release. Tool contracts may change between alpha releases; every change is
+> recorded in [CHANGELOG.md](CHANGELOG.md) with an upgrade note. Review the
+> [security policy](SECURITY.md) and each connector's guarantees before deployment.
+
+## Why a separate package
+
+- The Runtime stays small and domain-agnostic; vendor APIs change faster than its core.
+- Connectors get their own release cadence, owners and security review.
+- Every connector is a plugin, so Studio sees it with no extra work.
+
+| Layer | Package | Contains |
+| --- | --- | --- |
+| Core | `algen-agent-runtime` | Contracts, `@tool`, presets, `Toolkit`, plugins, `describe`, MCP and HTTP adapters |
+| Connectors | `algen-agent-tools` | Generic toolkits, one optional extra each |
+| Domain packs | Their own packages | Product-specific tools (hiring, text-to-SQL, HR, ...) |
+
+## Install
+
+Python 3.12 or 3.13. Install the package with the extra for each connector you use:
+
+```bash
+pip install "algen-agent-tools[postgres]"        # one connector
+pip install "algen-agent-tools[all]"             # every connector
+```
+
+The package supports `algen-agent-runtime>=0.1.0a11,<0.2`; see
+[compatibility](docs/compatibility.md).
+
+## Use a connector
+
+Name the connector's plugin in `domain_plugins`, trust the package's prefix, enable the tools
+and grant their permissions:
+
+```yaml
+agents:
+  - name: assistant
+    version: 1.0.0
+    description: Checks that tools are wired up
+    system_instructions: Use sample.echo when asked to echo text.
+    default_model: {name: m, provider: demo}
+    domain_plugins: [algen_agent_tools.sample]
+    enabled_tools: [sample.echo]
+    tool_permissions: [sample.read]
+security:
+  trusted_plugin_prefixes: [algen_agent_tools]
+```
+
+Then check the project the way Studio will:
+
+```bash
+algen-agent-runtime check agent.yaml
+algen-agent-runtime describe --config agent.yaml --json
+```
+
+Each zero-configuration plugin reads its settings from `env://` references at the moment its
+client first opens, never at import. To configure a connector in code (another name, other
+environment variables, a fake for tests), build its toolkit in your own plugin:
+
+```python
+from algen_agent_runtime.plugins.sdk import PluginManifest, plugin
+from algen_agent_tools.sample import sample_toolkit
+
+
+@plugin(PluginManifest(name="acme.tools", version="1.0.0", publisher="acme"))
+class AcmeTools:
+    def register(self, context):
+        sample_toolkit(name="diagnostics").register(context)
+```
+
+## Connectors
+
+| Connector | Plugin | Extra | Tools | Docs |
+| --- | --- | --- | --- | --- |
+| PostgreSQL | `algen_agent_tools.postgres` | `postgres` | `postgres.list_tables`, `postgres.describe_table` (read), plus your own typed queries | [postgres](docs/connectors/postgres.md) |
+| SMTP | `algen_agent_tools.smtp` | `smtp` | `smtp.send_email` (external) | [smtp](docs/connectors/smtp.md) |
+| Gmail | `algen_agent_tools.gmail` | `gmail` | `gmail.list_messages` (read), `gmail.send_email` (external) | [gmail](docs/connectors/gmail.md) |
+| Sample | `algen_agent_tools.sample` | none | `sample.echo` (read) | [sample](docs/connectors/sample.md) |
+
+### MCP servers
+
+For services with a well-maintained MCP server, `algen_agent_tools.mcp` adds a
+[governance overlay](docs/mcp-overlays.md) instead of a native client: a reviewed mapping that
+declares each remote tool's side effect, permission, approval rule and pinned input schema. The
+tools appear in `describe` and Studio before anything connects, undeclared tools are never
+exposed, and a tool whose schema changes is refused until it is reviewed again.
+
+```bash
+pip install "algen-agent-tools[mcp]"
+python -m algen_agent_tools.mcp snapshot server.yaml --name github --output github.overlay.yaml
+```
+
+Moving from the Runtime's built-in email and database connectors? See
+[migrating from the Runtime](docs/migrating-from-runtime.md).
+
+Proposed connectors follow the [connector policy](docs/connector-policy.md): at least two
+projects need it, it holds no domain logic, it has an owner and it passed a security review.
+When a well-maintained MCP server exists, the package ships a governance overlay instead of a
+native client.
+
+## Rules every connector follows
+
+- Narrow, typed actions (`list_open_invoices`, `post_message`), never a raw passthrough such as
+  free-form SQL or arbitrary HTTP.
+- Side effect, permission, idempotency, retries and timeout come from a Runtime preset.
+  Anything that writes, sends or deletes is keyed by the idempotency key and tried once.
+- Secrets are `env://` references only, resolved when a client opens.
+- An in-memory fake for offline tests; live tests run only when `ALGEN_TOOLS_LIVE=1`.
+- Every toolkit passes `algen_agent_tools.testing.assert_toolkit_contract`.
+
+## Development
+
+```bash
+python3.12 -m venv .venv
+source .venv/bin/activate
+python -m pip install --upgrade pip
+python -m pip install -e '.[dev]'
+make check
+```
+
+See [CONTRIBUTING.md](CONTRIBUTING.md), [writing a connector](docs/writing-a-connector.md) and
+[the release process](docs/releasing.md).
+
+## Security
+
+Report vulnerabilities privately as described in [SECURITY.md](SECURITY.md). Do not open a public
+issue.
+
+## License
+
+[Apache License 2.0](LICENSE).

algen_agent_tools-0.1.0a1/README.md

@@ -0,0 +1,153 @@
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/AlgenAI/algen-agent-tools/refs/heads/main/docs/assets/brand/banner-dark.svg">
+  <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/AlgenAI/algen-agent-tools/refs/heads/main/docs/assets/brand/banner-light.svg">
+  <img alt="Algen Agent Tools — Typed tools for agents. Governed by default." src="https://raw.githubusercontent.com/AlgenAI/algen-agent-tools/refs/heads/main/docs/assets/brand/banner-light.svg">
+</picture>
+
+# Algen Agent Tools
+
+[![Quality](https://github.com/AlgenAI/algen-agent-tools/actions/workflows/quality.yml/badge.svg)](https://github.com/AlgenAI/algen-agent-tools/actions/workflows/quality.yml)
+[![Security](https://github.com/AlgenAI/algen-agent-tools/actions/workflows/security.yml/badge.svg)](https://github.com/AlgenAI/algen-agent-tools/actions/workflows/security.yml)
+[![PyPI](https://img.shields.io/pypi/v/algen-agent-tools.svg)](https://pypi.org/project/algen-agent-tools/)
+[![Python 3.12+](https://img.shields.io/badge/python-3.12%2B-blue.svg)](https://www.python.org/downloads/)
+[![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+
+Curated, governed connectors for agents built on
+[Algen Agent Runtime](https://github.com/AlgenAI/algen-agent-runtime).
+
+Each connector is a Runtime `Toolkit` of narrow, typed actions, registered through a declared
+plugin. An agent names the plugin in `agent.yaml`, the Runtime checks every tool it enables, and
+Algen Agent Studio lists each tool with its side effect, permissions and environment variables
+from `algen-agent-runtime describe`, without running project code.
+
+> [!IMPORTANT]
+> `0.1.0a1` is a pre-release. Tool contracts may change between alpha releases; every change is
+> recorded in [CHANGELOG.md](CHANGELOG.md) with an upgrade note. Review the
+> [security policy](SECURITY.md) and each connector's guarantees before deployment.
+
+## Why a separate package
+
+- The Runtime stays small and domain-agnostic; vendor APIs change faster than its core.
+- Connectors get their own release cadence, owners and security review.
+- Every connector is a plugin, so Studio sees it with no extra work.
+
+| Layer | Package | Contains |
+| --- | --- | --- |
+| Core | `algen-agent-runtime` | Contracts, `@tool`, presets, `Toolkit`, plugins, `describe`, MCP and HTTP adapters |
+| Connectors | `algen-agent-tools` | Generic toolkits, one optional extra each |
+| Domain packs | Their own packages | Product-specific tools (hiring, text-to-SQL, HR, ...) |
+
+## Install
+
+Python 3.12 or 3.13. Install the package with the extra for each connector you use:
+
+```bash
+pip install "algen-agent-tools[postgres]"        # one connector
+pip install "algen-agent-tools[all]"             # every connector
+```
+
+The package supports `algen-agent-runtime>=0.1.0a11,<0.2`; see
+[compatibility](docs/compatibility.md).
+
+## Use a connector
+
+Name the connector's plugin in `domain_plugins`, trust the package's prefix, enable the tools
+and grant their permissions:
+
+```yaml
+agents:
+  - name: assistant
+    version: 1.0.0
+    description: Checks that tools are wired up
+    system_instructions: Use sample.echo when asked to echo text.
+    default_model: {name: m, provider: demo}
+    domain_plugins: [algen_agent_tools.sample]
+    enabled_tools: [sample.echo]
+    tool_permissions: [sample.read]
+security:
+  trusted_plugin_prefixes: [algen_agent_tools]
+```
+
+Then check the project the way Studio will:
+
+```bash
+algen-agent-runtime check agent.yaml
+algen-agent-runtime describe --config agent.yaml --json
+```
+
+Each zero-configuration plugin reads its settings from `env://` references at the moment its
+client first opens, never at import. To configure a connector in code (another name, other
+environment variables, a fake for tests), build its toolkit in your own plugin:
+
+```python
+from algen_agent_runtime.plugins.sdk import PluginManifest, plugin
+from algen_agent_tools.sample import sample_toolkit
+
+
+@plugin(PluginManifest(name="acme.tools", version="1.0.0", publisher="acme"))
+class AcmeTools:
+    def register(self, context):
+        sample_toolkit(name="diagnostics").register(context)
+```
+
+## Connectors
+
+| Connector | Plugin | Extra | Tools | Docs |
+| --- | --- | --- | --- | --- |
+| PostgreSQL | `algen_agent_tools.postgres` | `postgres` | `postgres.list_tables`, `postgres.describe_table` (read), plus your own typed queries | [postgres](docs/connectors/postgres.md) |
+| SMTP | `algen_agent_tools.smtp` | `smtp` | `smtp.send_email` (external) | [smtp](docs/connectors/smtp.md) |
+| Gmail | `algen_agent_tools.gmail` | `gmail` | `gmail.list_messages` (read), `gmail.send_email` (external) | [gmail](docs/connectors/gmail.md) |
+| Sample | `algen_agent_tools.sample` | none | `sample.echo` (read) | [sample](docs/connectors/sample.md) |
+
+### MCP servers
+
+For services with a well-maintained MCP server, `algen_agent_tools.mcp` adds a
+[governance overlay](docs/mcp-overlays.md) instead of a native client: a reviewed mapping that
+declares each remote tool's side effect, permission, approval rule and pinned input schema. The
+tools appear in `describe` and Studio before anything connects, undeclared tools are never
+exposed, and a tool whose schema changes is refused until it is reviewed again.
+
+```bash
+pip install "algen-agent-tools[mcp]"
+python -m algen_agent_tools.mcp snapshot server.yaml --name github --output github.overlay.yaml
+```
+
+Moving from the Runtime's built-in email and database connectors? See
+[migrating from the Runtime](docs/migrating-from-runtime.md).
+
+Proposed connectors follow the [connector policy](docs/connector-policy.md): at least two
+projects need it, it holds no domain logic, it has an owner and it passed a security review.
+When a well-maintained MCP server exists, the package ships a governance overlay instead of a
+native client.
+
+## Rules every connector follows
+
+- Narrow, typed actions (`list_open_invoices`, `post_message`), never a raw passthrough such as
+  free-form SQL or arbitrary HTTP.
+- Side effect, permission, idempotency, retries and timeout come from a Runtime preset.
+  Anything that writes, sends or deletes is keyed by the idempotency key and tried once.
+- Secrets are `env://` references only, resolved when a client opens.
+- An in-memory fake for offline tests; live tests run only when `ALGEN_TOOLS_LIVE=1`.
+- Every toolkit passes `algen_agent_tools.testing.assert_toolkit_contract`.
+
+## Development
+
+```bash
+python3.12 -m venv .venv
+source .venv/bin/activate
+python -m pip install --upgrade pip
+python -m pip install -e '.[dev]'
+make check
+```
+
+See [CONTRIBUTING.md](CONTRIBUTING.md), [writing a connector](docs/writing-a-connector.md) and
+[the release process](docs/releasing.md).
+
+## Security
+
+Report vulnerabilities privately as described in [SECURITY.md](SECURITY.md). Do not open a public
+issue.
+
+## License
+
+[Apache License 2.0](LICENSE).

algen_agent_tools-0.1.0a1/docs/assets/brand/README.md

@@ -0,0 +1,19 @@
+# Tools brand assets
+
+| Asset | Background | Intended use |
+| --- | --- | --- |
+| `logo-light.svg` | Transparent | Wordmark on a light surface |
+| `logo-dark.svg` | Transparent | Wordmark on a dark surface |
+| `logo-light-background.svg` | Included light panel | Portable light presentation |
+| `logo-dark-background.svg` | Included dark panel | Portable dark presentation |
+| `banner-light.svg` | Included | README and social header on light themes |
+| `banner-dark.svg` | Included | README and social header on dark themes |
+
+The mark is a governed core wired to four connector ports; each wire passes through a gate.
+It pairs with the Runtime's execution-graph mark: the Runtime runs agents, Tools connect them to
+the systems they act on, and every connection is governed. Keep the logo aspect ratio and the
+accessible title and description; do not remove the gates or recolor individual ports.
+
+Colors follow the Algen palette used by `algen.ai`, Agent Runtime and Agent Studio: gold
+gradients (`#F3D98B` → `#D4A017` → `#B8860B`), warm charcoal (`#0C0C0B` → `#2A2418`), ivory
+surfaces (`#FDFCF9` → `#F4EFE3`), and accessible ink or ivory text for the selected background.