Requests

Request a Tool

Missing a tool? Describe the deterministic job you keep doing and it may become the next one. Agents can ask for tools for themselves over the API, MCP or A2A.

Requests are stored so they can be read and answered. Please don't include secrets or other people's personal data.

Keyboard shortcuts

Esc
Close a menu or overlay, then leave full screen
↓ on a menu
Open it; ↑ ↓ move through its items
← → in the menu bar
Move between menus

Where your data goes
Using this page Using the API, MCP or A2A
Where it runs Nothing is computed. The form sends what you type to this site's API when you press **Send request**, after a Cloudflare Turnstile check that you are a person. In a Cloudflare Pages Function at the Cloudflare data centre nearest the caller.
What leaves your device What you submit (and your credentials) goes to this site's API when you press the button, and nowhere else: the page's Content-Security-Policy allows connect-src 'self' only.

Unlike the other operations, the server stores what you send here (title, problem, examples and category), with your client ID and the time, so the request can be reviewed and answered. It is not shared with other clients, except that a request marked planned, building or shipped may appear by title as related to similar requests. Do not include secrets or personal data. Only the per-call metadata row is logged.

The server reads the tool requests stored under your client ID and returns them. Nothing you send is stored.
Stored As for the API (right). **Your request is stored** (title, description, examples, category, and your email if you give one), because a request exists to be read and answered. With the API, MCP or A2A it is stored with your client ID; from the form, without one. Nothing else you send is stored. Don't include secrets or other people's personal data.
Logged As for the API (right). Only the per-call metadata above, attributed to your client ID. Never parameters, bodies, results, or credentials. Cloudflare, as the host, also processes request metadata (IP address, full URL including the query string, headers) under its own policies, so put inputs in POST bodies.
Access Requires a client ID and secret. Requires a client ID and secret (how to get one). HTTPS only; TLS terminates at Cloudflare.

Details and how to verify this yourself: Security & privacy.

User guide

The tool sits in a window that works like a desktop app: menus on the top row and the full-screen icon at its right (Esc leaves full screen). Help → Keyboard shortcuts… lists the keys.

This toolbox grows by request. If you, or an agent you run, keep doing the same deterministic job by hand (a conversion, a check, a calculation, a parser with exactly one right answer), ask for it here.

  1. Name the tool, e.g. IBAN validator or Semantic version compare.
  2. Say what it should do: the job, why you need it, and how you do it today.
  3. Give an example input and the output you expect. Concrete examples are the single best way to get a tool built: they become its first test.
  4. Optionally leave an email for a reply, then press Send request (or File → Send request).

You get a reference (tr_…). If a similar request is already planned, building or shipped, it is listed, and a shipped one may already do the job.

For agents. Agents can ask for tools for themselves, with their own credentials (which agents can register for without a person):

  • HTTP: POST /api/tools/request with title, problem, and optionally example_input, expected_output and category. GET /api/tools/requests lists your requests and their status.
  • MCP: the tools tool_request and tool_requests.
  • A2A: the skills tool_request and tool_requests.

A good moment to call tool_request is when you notice you are reasoning your way through something a function should answer.

Specification

What happens to a request. Each one is read by the owner and gets a status: received (not reviewed yet), planned, building, shipped (with the tool’s URL), declined or duplicate, often with a short note. Agents see these through tool_requests. Form requests are not linked to an identity, so the only follow-up is by the email you leave, if any.

What makes a good tool here. Deterministic (same input, same output), useful to more than one caller, and safe to run without secrets. Tools that would need to store your data, accept private keys or passwords, or act on other systems are declined: see Security & privacy.

Limits. Title up to 120 characters; description and each example up to 4,000. Each API client can make 20 requests per 24 hours. The form needs the Turnstile check to pass.

Related requests. When you submit, titles of accepted requests (planned, building or shipped) that share words with yours are returned, without who asked for them. Requests that are only received, or declined, are never shown to anyone else.

API & MCP

The same logic is available over HTTP and as MCP tools. Unlike this page, these run on the server: see where your data goes.

GET POST /api/tools/request Ask for a new deterministic tool to be added to this service, describing the job and an example. MCP tool tool_request · 5 parameters · full reference → GET POST /api/tools/requests See the tool requests you have made with these credentials and what became of each. MCP tool tool_requests · 0 parameters · full reference →