{
  "id": 15907441,
  "title": "Lawful Agents, Part 1: Your agent is reading an API that was never written for it",
  "url": "https://urgent.news/2026/10/21/lawful-agents-part-1-your-agent-is-reading-an-api-that-was-never",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-21T15:22:11.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/obinnaspeaks/lawful-agents-part-1-your-agent-is-reading-an-api-that-was-never-written-for-it-30ng"
  },
  "original_language": "en",
  "account": "This article series focuses on creating trustworthy agents that can interact with enterprise systems, specifically using Workday's Agent-Ready MCP tools. These tools differ from traditional enterprise APIs in several key ways. Firstly, their schemas are flat, meaning there is less structure to navigate, resulting in fewer tokens spent parsing, faster responses, and less room for the model to make up information. Secondly, every tool describes itself, carrying metadata about its function and expected parameters. This allows the agent to receive error information that helps it fix values on the next attempt. Lastly, these tools follow a standard called MCP JSON-RPC 2.0, which is supported by a single endpoint for each tenant, simplifying the connection process for the agent.\n\nFor developers, the interesting aspect is that they can utilize these tools regardless of the underlying platform. Agents built with platforms like Claude, Cursor, Copilot Studio, or Google Agentspace can call the same tools as Workday's Custom Agents. However, registering a third-party agent in Workday's Agent System of Record (ASOR) is necessary, and the registration process involves providing a list of allowed tools in the agent definition. If a write tool depends on other prompt tools, all of them must be included in the agent definition for the write operation to complete successfully.\n\nThe MCP Explorer on developer.workday.com is a helpful resource to find the necessary tools, filter by type, and retrieve the required tool IDs. Alternatively, the ASOR Agent Resource Search API allows for programmatic access to this catalogue using an API call.",
  "summary": "If you have ever pointed an agent at an enterprise API, you will know how it goes. The response comes back five levels deep, the model spends half its context working out where the manager's name lives, it retries when a field is not where it expected, and eventually it fills the gap with something it made up. Then you spend the afternoon wondering whether the problem is your prompt. It usually…",
  "key_points": [
    "Workday's Agent-Ready MCP tools differ from traditional APIs in schema structure and error handling.",
    "Tools follow MCP JSON-RPC 2.0 standard with single endpoint per tenant for simplified connection.",
    "Registration required for third-party agents in Workday's Agent System of Record (ASOR)."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}