{"canonical_url":"https://engineer.company/ai-tools/","content_markdown":"# Your software as tools for AI agents\n\nGive AI agents a defined way to use the business software you already run.\nWe identify suitable operations, describe their inputs and results, and apply\npermission checks before exposing them as tools. Changes are planned alongside\nthe existing application, with testing and a rollout agreed for its operational\nconstraints.\n\n## Unpicked: the rules out of the screens\n\nThe rules that run a business hide in the software: in a form's validation, in a\nstored procedure, in a report nobody dares to change, in the head of the person\nwho built it. We find them, write them down and move each into one layer — often\nthe database itself — where every caller gets the same\nanswer. The screen, the agent and the partner integration then use the same implemented rules instead of maintaining separate versions.\n\n## Exposed: described tools an agent can call\n\nEach operation an agent should have is offered as a tool named for the work —\nbook a slot, quote a price, release an order — with typed inputs, errors an agent\ncan act on, and [idempotent](/glossary/#idempotent) calls so a retry never books\ntwice. The description is an [OpenAPI](/glossary/#openapi) document generated\nfrom the code, and an MCP server offers the same operations to the agents that\nspeak it. [Authentication](/glossary/#authentication) is OAuth, so an agent acts\nfor a user without a password changing hands, and only within that user's\n[rights](/ai-security/).\n\n## Roll out operations in controlled steps\n\nWe expose selected operations alongside the existing application and compare\nthe new path with the current behavior. Slow work can move onto a\n[queue](/glossary/#queue) where appropriate. Dependencies, migration needs,\nmaintenance windows and rollback are assessed before rollout. Existing screens\nremain available where the agreed architecture allows; any interruption is\nplanned with the people who run the service.\n\n## Generate the contract and check for drift\n\nWhere the architecture supports it, we generate the description from the\ndatabase and [API](/glossary/#api) definitions and\ncompare the published contract with the implementation. Checks identify\nmismatches in the covered operations and make compatibility changes visible\nin review. The tests and their coverage are part of the handover; a generated\ndescription alone does not prove every behavior correct.\n\n## The work behind it\n\nWe have opened up large systems this way. We\n[generated an API contract from the database out](/portfolio/generated-the-api-contract-from-the-database-out/),\nwith a guard at every hop, and\n[migrated an API of 760 operations at 100% parity](/portfolio/migrated-the-api-to-huma-v2-at-100-parity/)\nwith its published description. We\n[designed a JSON passthrough from PostgreSQL to the API](/portfolio/designed-a-json-passthrough-from-postgres-to-api/),\n[built a platform in clean layers](/portfolio/a-maritime-platform-built-in-clean-layers/)\nwith its business rules in one place,\n[moved slow work onto a job queue](/portfolio/moved-slow-work-onto-a-river-job-queue/),\nand [built the operator back office](/portfolio/built-the-operator-back-office-for-the-platform/)\nthat runs it without database access.\n\n## How an engagement runs\n\nIt starts with a list: what your people do in the software every day, ranked by\nhow often and how much it costs them. We take the first few operations, find\ntheir rules, and expose them as described tools behind tests and permissions,\nrunning beside the screens rather than instead of them. Then the next few. Your\nteam keeps the code, the tests and the description; the tools can be called by\n[an agent built for your trade](/ai-agents/), by the assistants your staff\nalready use, or by a partner's system. It is bought like the rest of our work,\non the terms in [what it costs](/what-it-costs/).\n\nIf your software only works when somebody clicks it,\n[tell us what it is](/contact/) *(read by the engineer)*.\n\n\u003chttps://engineer.company/ai-tools/\u003e\n","date_modified":"2026-11-12T05:34:23Z","description":"Expose selected software operations as described tools for AI agents, with permissions, contract checks and a planned rollout.","formats":{"gemtext":"https://software.engineer.company/ai-tools/index.gmi","gopher":"https://software.engineer.company/ai-tools/gophermap","html":"https://software.engineer.company/ai-tools/","json":"https://software.engineer.company/ai-tools/index.json","markdown":"https://software.engineer.company/ai-tools/index.md","pdf":"https://software.engineer.company/ai-tools/index.pdf"},"kind":"page","language":"en","title":"Your software as tools for AI agents","url":"https://software.engineer.company/ai-tools/","version":1}