Search the docs

Search guides, API endpoints and MCP tools.

Planning

get_agent_instructions

Read grantRead-onlyIdempotent

Get the instructions to follow before writing a ticket's summary (ticket), its plan (plan), test cases (test-cases), specs (test-code), a product's Fixture API (fixtures) or the CI that runs tests (test-ci): templates, guidance and, for tickets, defaults. Name the team the work belongs to; source says whether they are the team's, the workspace's or Clanker Ship's. Returns the instructions and who last changed them. Needs read access.

Inputs

kindstringRequired

What the instructions shape: ticket for a ticket's summary, plan for its plan, test-cases for test cases, test-code for specs, fixtures for a product's Fixture API and test-ci for the CI that runs tests.

One ofticketplantest-casestest-codefixturestest-ci
teamstring

The team the work belongs to, such as WEB. Leave it out for the workspace's instructions.

tools/callJSON-RPC
{  "jsonrpc": "2.0",  "id": 1,  "method": "tools/call",  "params": {    "name": "get_agent_instructions",    "arguments": {      "kind": "ticket",      "team": "WEB"    }  }}
POST/agent/v1/agent-instructions:get
curl -X POST https://api.qa.clankership.net/agent/v1/agent-instructions:get \  -H "Authorization: Bearer $CLANKER_AGENT_TOKEN" \  -H "Content-Type: application/json" \  -d '{    "kind": "ticket",    "team": "WEB"  }'
The same call over the agent HTTP API. Set CLANKER_AGENT_TOKEN to an agent OAuth access token.