{
  "title": "XML Namespace Inspector",
  "human_url": "https://happytails.ai/en/developer-tools/xml-namespace-inspector/",
  "agent_url": "https://happytails.ai/agents/en/developer-tools/xml-namespace-inspector/",
  "language": "en",
  "markdown_url": "https://happytails.ai/en/developer-tools/xml-namespace-inspector.md",
  "content": "XML Namespace Inspector\nFind unresolved XML prefixes and conflicting namespace declarations locally. Review the exact declarations before you ship a document.\nHow can we improve this tool?\nReport a problem or share an idea.\nPlease leave out private information. Your message and the tool name go to our team via PostHog.\nHow to use XML Namespace Inspector\nPaste the XML.\nRun the local check.\nReview declarations, conflicts and unresolved prefixes, then download the report.\nWhat it checks\nThe inspector compares prefixes used by element and attribute names with xmlns declarations. It does not fetch external schemas.",
  "content_format": "text/plain",
  "visibility": "public",
  "links": [],
  "tool": {
    "id": "xml-namespace-inspector",
    "category": "developer-tools",
    "built": true,
    "requirements": "Input is limited to 200000 characters. Results are computed locally and exported as JSON.",
    "implementation": {
      "fields": [],
      "inputMaxLength": 200000,
      "inputErrorCode": "STRUCTURED_TEXT_TOO_LONG",
      "registrationFamily": "xml-namespace-inspector",
      "note": "Find unresolved prefixes and conflicting XML namespace declarations locally.",
      "experience": {
        "automatic": false,
        "single": false,
        "inputMaxLength": 200000,
        "inputMode": "text",
        "label": "XML",
        "placeholder": "<item><name>Ada</name></item>",
        "help": "Include one root element and matching closing tags. Up to 200,000 characters. Review the settings before running.",
        "action": null
      },
      "mode": "explicit",
      "interactive": false
    },
    "execution": "Browser interface",
    "api": null,
    "browser_agent": {
      "supported": true,
      "name": "run_current_tool",
      "discovery": "WebMCP on the human page in a supporting browser",
      "verification": "See audit/API-AUDIT.md; availability is not verification"
    }
  },
  "markdown": "# XML Namespace Inspector\n\n- Human page: https://happytails.ai/en/developer-tools/xml-namespace-inspector/\n- Markdown: https://happytails.ai/en/developer-tools/xml-namespace-inspector.md\n- Structured JSON: https://happytails.ai/agents/en/developer-tools/xml-namespace-inspector/index.json\n- Visibility: public\n\n## Tool capabilities\n\n| Property | Value |\n| --- | --- |\n| Tool ID | `xml-namespace-inspector` |\n| Category | developer-tools |\n| Implementation | Registered implementation. Registration alone is not a production-quality guarantee. |\n| Browser execution | Use the visible action or interactive controls. |\n| Browser processing | Browser; see tool notes for network behavior. |\n| HTTP API | Not callable through HTTP. |\n| Browser-agent interface | run_current_tool |\n\n### Implementation notes\n\nFind unresolved prefixes and conflicting XML namespace declarations locally.\n\n### Inputs and settings\n\nText input: XML.\n\nExample or placeholder shown in the interface (not a validated fixture):\n\n```text\n<item><name>Ada</name></item>\n```\n\nInclude one root element and matching closing tags. Up to 200,000 characters. Review the settings before running.\n\nNo additional settings are declared for this tool.\n\n### Browser-agent workflow\n\n1. Open the human page in a browser that supports WebMCP.\n2. Discover the interface exposed by that page; use its actual schema.\n3. Select files on the page first when the tool requires files.\n4. Call `run_current_tool` with valid input and settings.\n5. Inspect the returned result or error and the displayed output. Retrieve files from the displayed download links.\n\nCalls do not automatically copy or download results. Browser permissions still apply. Interface availability alone is not proof of successful execution.\n\n### Planning specification\n\nInput is limited to 200000 characters. Results are computed locally and exported as JSON.\n\nThis describes intended requirements. Use the implementation notes, interface schema and observed output to determine current support.\n\n### Complete machine-readable capability record\n\n```json\n{\n  \"id\": \"xml-namespace-inspector\",\n  \"category\": \"developer-tools\",\n  \"built\": true,\n  \"requirements\": \"Input is limited to 200000 characters. Results are computed locally and exported as JSON.\",\n  \"implementation\": {\n    \"fields\": [],\n    \"inputMaxLength\": 200000,\n    \"inputErrorCode\": \"STRUCTURED_TEXT_TOO_LONG\",\n    \"registrationFamily\": \"xml-namespace-inspector\",\n    \"note\": \"Find unresolved prefixes and conflicting XML namespace declarations locally.\",\n    \"experience\": {\n      \"automatic\": false,\n      \"single\": false,\n      \"inputMaxLength\": 200000,\n      \"inputMode\": \"text\",\n      \"label\": \"XML\",\n      \"placeholder\": \"<item><name>Ada</name></item>\",\n      \"help\": \"Include one root element and matching closing tags. Up to 200,000 characters. Review the settings before running.\",\n      \"action\": null\n    },\n    \"mode\": \"explicit\",\n    \"interactive\": false\n  },\n  \"execution\": \"Browser interface\",\n  \"api\": null,\n  \"browser_agent\": {\n    \"supported\": true,\n    \"name\": \"run_current_tool\",\n    \"discovery\": \"WebMCP on the human page in a supporting browser\",\n    \"verification\": \"See audit/API-AUDIT.md; availability is not verification\"\n  }\n}\n```\n\n## Page guide\n\nFind unresolved XML prefixes and conflicting namespace declarations locally. Review the exact declarations before you ship a document.\n\nHow can we improve this tool?\n\nReport a problem or share an idea.\n\nPlease leave out private information. Your message and the tool name go to our team via PostHog.\n\n### How to use XML Namespace Inspector\n\n1. Paste the XML.\n2. Run the local check.\n3. Review declarations, conflicts and unresolved prefixes, then download the report.\n\n## What it checks\n\nThe inspector compares prefixes used by element and attribute names with xmlns declarations. It does not fetch external schemas.\n"
}