What the caller may do here
Role, gate state, plan limits and a set of derived booleans — so an agent on a static surface can check before it acts instead of attempting a write and reading the failure.
Descriptive, never authoritative: see the schema.
Authorizations
MCPJam API key (sk_…). Create one at Settings → API keys. Guest sessions cannot use the API, and API keys cannot manage other API keys.
Response
The caller's capabilities in this project.
What the caller may do in this project, asked BEFORE they try it.
A planning aid, not a gate. Every enforcement point is unchanged: the write path checks roles and the beta flag inside the platform regardless of what this returned a second earlier. A caller that reads a true here and races a flag flip gets the same clean 403 it would have got without asking. Nothing may consult this INSTEAD of its own check.
It exists because every agent surface MCPJam ships is static — one MCP tool catalog built with no organization in hand, a CLI command tree fixed at install — so an agent planning a task otherwise has to attempt the write and read the failure. By then it has usually already told a human what it was about to do.
The eval vocabulary this deployment understands (see the x-mcpjam-eval-vocabulary header). Absent on a deployment that predates the negotiation, which then speaks only vocabulary 1. Each fields entry lists the LEGACY spellings a vocabulary-2 body may still use for that canonical field; a canonical spelling sent together with one of its legacy spellings is refused. iterations is deliberately absent from legacyIterations: under vocabulary 2 that key is the exact count, not the floor.
The resource-noun VALUE vocabulary this deployment understands (see the x-mcpjam-api-vocabulary header). Absent on a deployment that predates the negotiation, which then speaks only vocabulary 1. SEPARATE from vocabulary above, which is eval-scoped by name and moves on its own schedule.

