whatisgithub

What is tools?

hacktronai/tools — explained in plain English

Analysis updated 2026-05-18

3TypeScriptAudience · developerComplexity · 2/5Setup · easy

In one sentence

A reference repository collecting the exact tool schemas different AI coding agents use, so developers can match a model's expected tool shape precisely.

Mindmap

mindmap
  root((Agent Tools))
    What it does
      Collects verbatim tool schemas
      Organizes them by provider
      Maps model IDs to providers
    Tech stack
      TypeScript
      JSON schemas
    Use cases
      Match a model's trained tool shape
      Build a compatible edit tool
      Browse schemas in a web UI
    Audience
      Developers
      AI agent builders

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Look up the exact JSON schema a specific AI coding agent uses for its edit tool.

USE CASE 2

Build a custom tool that matches a model's trained schema shape to avoid performance loss.

USE CASE 3

Browse collected tool schemas across providers using the included web interface.

USE CASE 4

Reference the pseudo-code implementations for string replacement and patch application edit tools.

What is it built with?

TypeScriptJSON

How does it compare?

hacktronai/tools000madz000/payload-test-api-route-handlerakash-sr/memobsidian
Stars333
LanguageTypeScriptTypeScriptTypeScript
Setup difficultyeasyeasymoderate
Complexity2/52/53/5
Audiencedeveloperdevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

This is a reference collection of JSON files rather than a runnable application.

License terms are not described in the shown README, check the repository's license file for exact terms.

So what is it?

HacktronAI/tools is a small reference repository that collects the tool schemas used by different AI coding agents. When a coding assistant like Claude Code or similar agents gives its underlying model access to tools, such as an edit tool for changing files, that tool has to be described to the model in a very specific shape, usually as a JSON schema listing the tool's name, what it does, and what parameters it expects. Different agent products define these tool shapes differently, even for the same underlying task. The README explains why this matters: if you hand a model a tool shaped differently than the one it was actually trained on, especially something as sensitive as an edit tool, you risk the model making mistakes or producing schema errors, which hurts its performance. This project exists to document those real, verbatim tool definitions from each agent so people can see exactly how each one is shaped, rather than guessing or reinventing them. The repository is organized by provider. Each provider gets its own folder containing a metadata file describing the provider, agent name, and version, along with individual JSON files for each tool describing its name, capability, description, and parameters. A separate mappings file links specific model IDs to their matching provider. There is also a folder with pseudo-code specifications for edit tool implementations, covering operations like string replacement and patch application, plus a sources document tracking where each schema definition came from. A small web interface is included that reads a public API file to let you browse the collected schemas. The intended use, per the README, is to hand one of these schemas to your own agent and ask it to build a working tool that matches that exact shape. The project is written in TypeScript and the README itself is quite sparse, focused mainly on explaining the folder layout rather than providing extensive documentation or examples.

Copy-paste prompts

Prompt 1
Show me the tool schema this repo has recorded for a specific AI coding agent's edit tool.
Prompt 2
Explain why giving a model a differently shaped tool than it was trained on can hurt performance.
Prompt 3
Help me build an edit tool using the pseudo-code spec in this repo's implementations folder.
Prompt 4
Walk me through how the mappings.json file links model IDs to their tool provider.

Frequently asked questions

What is tools?

A reference repository collecting the exact tool schemas different AI coding agents use, so developers can match a model's expected tool shape precisely.

What language is tools written in?

Mainly TypeScript. The stack also includes TypeScript, JSON.

What license does tools use?

License terms are not described in the shown README, check the repository's license file for exact terms.

How hard is tools to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is tools for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.