records_status
Read onlyThe game's verified player records: the declared kinds (type, max_bytes and max_per_player, or min and max), when and by whom they were set, usage per day and environment from the game's record store (rows read and written, requests) with the bytes stored, what that costs at cost, and the ceilings a kind can be set to.
/api/agent/records/statusBehavior
The game's verified player records: the declared kinds (type, max_bytes and max_per_player, or min and max), when and by whom they were set, usage per day and environment from the game's record store (rows read and written, requests) with the bytes stored, what that costs at cost, and the ceilings a kind can be set to. Read it before records_configure and when the creator asks what records hold or cost.
Input parameters
This tool takes no arguments. Send an empty object: {}.
The descriptions above include conditional requirements. The full schema below shows structural validation; runtime checks also apply.
JSON Schema
{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"properties": {},
"additionalProperties": false
}Use its name in your connected MCP client. For the HTTP API, the route is relative to your Convex site URL and requires your agent key as a bearer token. Keep the key on the agent side, outside a game build.