Evidence row 307025

What was observed

{
  "count": 6,
  "tools": [
    {
      "description": "List every active listing category as a flat catalog. Each entry has a numeric id, a dot-separated path encoding its place in the hierarchy (for example vozila.automobili is a child of vozila), and a human-readable title in Serbian. Call this first to translate what a user is looking for into a category id, then call get_category to learn which attributes that category supports.",
      "inputSchema": {
        "properties": {},
        "required": [],
        "type": "object"
      },
      "name": "get_categories"
    },
    {
      "description": "Describe one category and the attributes listings in it can be filtered by. Each attribute has a name (the key to use when filtering), a label, and a type giving the JSON value a filter must supply: string, number, boolean or date (ISO 8601). An attribute may also carry options, which are the only accepted values for it; value_type with min and max, bounding what numbers are accepted; or a picklist_path, whose accepted values are not listed here and must be fetched with get_picklist_values. A picklist_depends_on names another attribute whose value narrows this one.",
      "inputSchema": {
        "properties": {
          "categoryId": {
            "description": "Numeric category id, as returned by get_categories",
            "format": "int64",
            "type": "integer"
          }
        },
        "required": [
          "categoryId"
        ],
        "type": "object"
      },
      "name": "get_category"
    },
    {
      "description": "Fetch one published listing by id, including its full description, price, location, category and stored attribute values. Attribute keys match the names reported by get_category for that listing's category, and attributes holds the raw stored values. Under the same key, attribute_labels gives that attribute's display label, plus a value label where the value comes from a fixed set such as a picklist or enum — use the labels when describing the listing to a user, and the raw values when filtering. Only public listings can be fetched.",
      "inputSchema": {
        "properties": {
          "listingId": {
            "description": "Numeric listing id, as returned by search_listings",
            "format": "int64",
            "type": "integer"
          }
        },
        "required": [
          "listingId"
        ],
        "type": "object"
      },
      "name": "get_listing"
    },
    {
      "description": "List the accepted values for an attribute whose get_category entry carries a picklist_path. These value sets are hierarchical and too large to inline, so they are fetched one level at a time. A picklist_path may contain a placeholder in braces naming another attribute, as in 'vehicles.car.{make}'; replace the placeholder with that attribute's chosen value before calling, so picking make 'toyota' means requesting 'vehicles.car.toyota' to get the models for it.",
      "inputSchema": {
        "properties": {
          "path": {
            "description": "Fully resolved dot-separated picklist path, with any placeholder already substituted",
            "type": "string"
          }
        },
        "required": [
          "path"
        ],
        "type": "object"
      },
      "name": "get_picklist_values"
    },
    {
      "description": "Search published listings by free text, category and location. Every argument is optional but at least one must be given; supplying several narrows the result the way a user ticking filters would.\n\ncategory_id and location_id are hierarchical and match the whole subtree beneath them, so the category 'Mobilni telefoni i oprema' also returns listings filed under its child categories, and Beograd also returns listings in Novi Beograd, Zemun and every other place under it. Filter at the broadest level the user actually meant, and only narrow when they named a specific place or category. Get ids from get_categories and search_locations.\n\nq is an ordinary keyword search, not semantic or vector search: it matches words the listing actually contains, so synonyms and paraphrases will not find anything. It matches broadly across titles, descriptions, attribute values and the listing's category and location names, but ranks titles and descriptions highest. Prefer q for what an item is, and the id filters for where it is and what it is filed under — 'stan Beograd' works, but a location_id for Beograd works better.\n\nOnly the first few best matches are returned and there is no way to page past them. If the result looks too broad, narrow the search and call again rather than asking for more.",
      "inputSchema": {
        "properties": {
          "categoryId": {
            "description": "Numeric category id from get_categories; matches this category and everything under it",
            "format": "int64",
            "type": "integer"
          },
          "limit": {
            "description": "Maximum results to return (1-10, default 10)",
            "format": "int32",
            "type": "integer"
          },
          "locationId": {
            "description": "Numeric location id from search_locations; matches this place and everything under it",
            "format": "int64",
            "type": "integer"
          },
          "q": {
            "description": "Keywords to match, for example 'iphone 15 pro'",
            "type": "string"
          }
        },
        "required": [],
        "type": "object"
      },
      "name": "search_listings"
    },
    {
      "description": "Find Serbian locations by name and return their numeric ids, which is how listings are filtered by place. Matching is fuzzy and tolerates missing diacritics. Results carry a level (COUNTRY, MUNICIPALITY, CITY, CITY_MUNICIPALITY, SETTLEMENT, NEIGHBOURHOOD) and a path showing where the place sits in the hierarchy; use both to pick between same-named places, and prefer asking the user rather than guessing when several look plausible.",
      "inputSchema": {
        "properties": {
          "limit": {
            "description": "Maximum results to return (1-25, default 10)",
            "format": "int32",
            "type": "integer"
          },
          "query": {
            "description": "Place name to search for, for example 'Novi Sad'",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "type": "object"
      },
      "name": "search_locations"
    }
  ]
}

What the leaf hashes

{"body":"d82e5731b6eb10874e85225bc407a4b0d63e5e860448243b12c2c1883a6e984e","id":307025,"kind":"mcp.tools","method":"probe.mcp/1","observed_us":1793057417652442,"prev":null,"subject":"619e1e6e-0459-455b-a29e-fffb65c4fc8a","subject_kind":"endpoint"}

Proof

Fold these into the leaf in order, hashing each sorted pair with keccak256, to reach the root of 2026-10-26 (296695 rows).

1. 0xa40f9c91b50337dc1efb0fd3c6270dc7bef1de760b939ebb0a41f0cb9ae4e17c
2. 0x716c94d26824dc86e04cd6be730297e061ae66c639433a6d7bac6d0bb7725014
3. 0xcdf4976f602b858aba5849f90523d34cd6b19bc6879c09c2bbb5c38f8c321197
4. 0x227074b7fbbdbf307cc8cabacb5e44daec839b82d929aac395fa9ecda619785f
5. 0x12a70ae626e36614851b14d7115cc043caf24b419b3a2e02ca25df7cfcdc0971
6. 0x14c212a47689d557a7738fafa70119c9a2006658ee224e3fbf1275daafb69f3e
7. 0xb02ff3036fe3986ac5272006a4ddd509593e1419cc8e60bab48ba961b5114835
8. 0xcf1be0ce1e98f9b6de8c60cc3b21f14ebdd13a1574ee95b7df0436c724ce1224
9. 0xc7f2f5b3daead6ffc6655816ed90d85a4642b08e84aa867c9b2ca924dc7a356c
10. 0x98005a23cbe74a9cdea08497a91d96ddecf46b8942b406963266e78529eea12d
11. 0xf02ec0f13d875e636ca9d24097cc2a185cdb09429c8c4ade598b8089f42bb140
12. 0x19537c574979327583a539261287714af2eee831125de819abab0f155acd3a75
13. 0xc34c13c58ba9c342ea1b833ac1882a4aea22777c4fd1092b2f83d3bac6b9f845
14. 0x428106f4ae4ec142f17aebf6fa50935242f8d3f1c211cf95d6351d03d11da2b7
15. 0x62a900133713919f4eed33d8336876b7a6d538233b8a4f3ed03b29aa44f5bad0
16. 0x1ac20d30773e1f4f2f811540e9a99b5cca9177c9e2e029acc0d80cf3f1d11f0f
17. 0xd21942ae3214eff88e08ab04884fd4b11958b51af9a0741b7668e2d07a2c56c9
18. 0x9a9024edb5069d88a324facb310a5ce8e495214bbaa968f077bede437390194f
19. 0x9b9ce5b74b9bab5121612ef6b64920a8d453cbf311096a423eef9702747e868a

Day root

0xf43e8dcc3d451a4788b26be904c55e8c4c0fa75c9666796c51db38d37e2c0df8

Chained

0x702d5ac508f08b0d1accf36af25822d8e5660367494edd17a642fb61e158a57a

Published

On Arc Testnet, block 69251483: 0x495162f8936e19f0039918feebe6c307f327cd6bf8c37219620b1970041fa9ae