get_library_brief_input

Inputs

{
  "type": "object",
  "properties": {
    "date": {
      "type": "string",
      "description": "UTC day, YYYY-MM-DD; not in the future."
    },
    "run_id": {
      "type": "string",
      "description": "Phase 2 run id (1-200 characters)."
    }
  },
  "additionalProperties": false,
  "required": [
    "date",
    "run_id"
  ]
}

Outputs and behavior

Prepare a dated library-status packet for a brief that the client writes. Use for a requested daily brief; use get_library_activity for direct metrics or get_playbook_input for topical research. Returns job_key, input_hash, bound revisions, counts, coverage, up to 20 work rows and five Librarian cards within 24,576 bytes. No work lease is acquired. Pass the unchanged packet to publish_library_brief after writing.

The registry does not publish an output schema for this tool. The description above is its documented behavior; response fields beyond it are not specified here.

Example call

Example tool name and arguments, generated from the input schema. Replace placeholder strings and sample numbers with your own values. This is a request template, not a recorded call or response.

{
  "name": "get_library_brief_input",
  "arguments": {
    "date": "YOUR_DATE",
    "run_id": "YOUR_RUN_ID"
  }
}

Clients

This tool is available to MCP clients using stdio or http.

The registry records transport support, not individual client test results. See the MCP setup reference for named clients, configuration, and tool-list limits.