List every tool name — no API key required
The one endpoint on this surface that needs no credentials, so an agent can confirm a tool name is real BEFORE the user has an account. Also served at /tools.json (and /tools.md) on this same host — this /api/tools-catalog path is the same handler and is documented here so it is reachable from the spec. Follow it on the host that served this spec: the catalog names submit and schema endpoints for whichever deployment answered, so fetching it from another host hands you that host's endpoints.
Returns the exact, case-sensitive type string to send to /submit-job, plus each tool's REQUIRED settings. Guessing a name is the most common way generated code fails, and an unrecognised settings key is never rejected, only flagged — so a synonym surfaces as "missing required field", not as an unknown-key error.
Deliberately NOT the whole schema: optional parameters, defaults and descriptions need a key (/tools/{name}/schema). Unlike /tools, this is not account-scoped — it lists what a brand-new public user could submit, so feature-flagged, domain-restricted and API-gated tools are omitted.
Request
- Base URL: https://app.tamarind.bio
- URL: https://app.tamarind.bio/api/tools-catalog
- Auth: none required
Query parameters
Return only this tool, so a caller that already knows the name does not have to pull the whole catalogue into context.
Return only tools carrying this intent tag (case-insensitive), e.g. protein-ligand-docking. The full tag list is in the tags field of every response.
md returns the catalogue as a Markdown table (text/markdown) instead of JSON.
Response
The public tool catalogue
Example response
{
"submitEndpoint": "POST https://<the-host-that-served-this>/api/submit-job (requires x-api-key)",
"mcpServer": "https://mcp.tamarind.bio/mcp",
"tools": [
{
"type": "alphafold",
"displayName": "AlphaFold",
"tags": [
"structure-prediction"
],
"taskSetting": "metricType"
}
]
}Changes
No recorded changes to this operation across all 1 revision of this API.