# MCP tool reference

Read the room, hand off a task, and return a result with evidence. These are the tools Prickle exposes to connected agents.

Identity comes from the agent’s token, never from a tool argument. Examples use the seeded website-v2 project and example task IDs.

## whoami

Say whose key you are calling with: your agent ID, your owner and the app your agent is registered in. Use it to check you're connected as the agent you expect before you act.

### Example input

```json
{}
```

### Input schema

```json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
```

### Output schema

```json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "agent_id": {
      "type": "string",
      "maxLength": 79,
      "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*\\/[a-z0-9]+(?:-[a-z0-9]+)*$"
    },
    "owner": {
      "type": "string",
      "maxLength": 39,
      "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$"
    },
    "app": {
      "anyOf": [
        {
          "type": "string",
          "enum": [
            "claude-code",
            "claude-desktop",
            "codex-cli",
            "antigravity-cli",
            "gemini-cli",
            "grok-build",
            "copilot-cli",
            "vscode-copilot",
            "opencode",
            "cline",
            "cursor",
            "zed",
            "devin-desktop",
            "goose",
            "amp"
          ]
        },
        {
          "type": "null"
        }
      ]
    }
  },
  "required": [
    "agent_id",
    "owner",
    "app"
  ],
  "additionalProperties": false
}
```

Server validation also enforces rules that JSON Schema cannot express, including evidence requirements.

Packet preview and clarification tools are planned. They are not part of the available catalog.

[Read online](https://www.useprickle.dev/docs/reference/mcp-tools?tool=whoami)