jajiga.com WebMCP audit

Rescan
audited Aug 28, 2026in 10s
64/ 100

2 tools registered. Strongest in usefulness, weakest in human experience.

WebMCP use68
Usefulness100
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
search_rooms: warning

search_rooms

Search for rental rooms and accommodations on jajiga. Returns a structured list of matching rooms with price, rating, photo, and URL. Use this when the user wants to find a place to stay in a specific city or location.Answers a question. Declared read only.
pagehttps://www.jajiga.com/
implementation
viaimperative
entry pointdocument
registered after2990ms
executepresent
api surface
cityrequired
checkinoptional
checkoutoptional
guestsoptional
min_priceoptional
max_priceoptional
orderoptional
tagsoptional
annotations
read onlytrue
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contentfalse
titlenot declared
3 findings
warningSchema quality
2 / 4
1 of 2 tool schemas are harder for an agent to use than they need to be: search_rooms 1 parameter description is over Chrome's 150-character guidance.
search_rooms: 1 parameter description is over Chrome's 150-character guidance
fix
{
  name: "search_rooms",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
warningUntrusted content hint
0 / 2
2 of 2 tools look like they return text written by other people but declare no untrustedContentHint, so an agent will treat the response as the site speaking.
search_rooms: user, rating; get_room: user, rating
fix
{ name: "search_rooms", annotations: { untrustedContentHint: true } }
warningHuman parity
0 / 8
2 of 2 tools run through the JavaScript API with no visible counterpart, so the person co-browsing cannot see what the agent is offered. Declarative forms (or at least a title annotation) close the gap.
search_rooms, get_room
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_rooms" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "search_rooms",
  "description": "Search for rental rooms and accommodations on jajiga. Returns a structured list of matching rooms with price, rating, photo, and URL. Use this when the user wants to find a place to stay in a specific city or location.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "city": {
        "type": "string",
        "description": "City or location name to search in, e.g. \"شیراز\" or \"Shiraz\""
      },
      "checkin": {
        "type": "string",
        "description": "Check-in date as ISO 8601 (YYYY-MM-DD), e.g. \"2026-07-01\""
      },
      "checkout": {
        "type": "string",
        "description": "Check-out date as ISO 8601 (YYYY-MM-DD). Defaults to checkin + 1 day if omitted."
      },
      "guests": {
        "type": "integer",
        "description": "Number of guests",
        "minimum": 1
      },
      "min_price": {
        "type": "number",
        "description": "Minimum price per night in Tomans"
      },
      "max_price": {
        "type": "number",
        "description": "Maximum price per night in Tomans"
      },
      "order": {
        "type": "string",
        "enum": [
          "similarity",
          "popularity",
          "rating",
          "low_price",
          "high_price",
          "books",
          "discount",
          "newest"
        ],
        "description": "Sort order for results"
      },
      "tags": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Feature tags: pool, jacuzzi, breakfast, scenic, waterfront, luxury, economic, instant, plus, pet, mountain, ecolog, ruralhome, swiss_cottage, wooden_cottage, etc."
      }
    },
    "required": [
      "city"
    ]
  },
  "annotations": {
    "readOnlyHint": true,
    "untrustedContentHint": false
  }
}
Showing search_rooms

Findings

WebMCP use

68 / 100 · weight 50
passTools registered
4 / 4
2 tools registered across 1 page.
failReal-browser eligible
0 / 8
The page's code registers these tools, but a real visitor's browser does not get them yet: WebMCP needs a native modelContext or a current origin trial token, and this page has neither.
warningRegistration timing
2 / 4
The slowest tool took 2990.2999999523163ms to register, past the 1000ms an agent reading the registry at first paint would wait for.
toolget_room
get_room: registered at 2990.2999999523163ms
fix
// Register tools as soon as they're ready, not behind a deferred/async chunk.
document.modelContext.provideContext({ tools: [/* ... */] });
passCanonical entry point
4 / 4
All 2 tools register on the canonical document.modelContext entry point.
passSchema validity
5 / 5
All 2 tools declare a structurally valid object input schema.
warningSchema quality
2 / 4
1 of 2 tool schemas are harder for an agent to use than they need to be: search_rooms 1 parameter description is over Chrome's 150-character guidance.
toolsearch_rooms
search_rooms: 1 parameter description is over Chrome's 150-character guidance
fix
{
  name: "search_rooms",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
passStub detection
5 / 5
All 2 tools declare an execute handler.
passAnnotations present
4 / 4
All 2 tools declare a readOnlyHint, so an agent knows which calls change state.
passAnnotation mismatch
3 / 3
No tool claims to be read-only while its name says it writes (2 declared hints checked).
warningUntrusted content hint
0 / 2
2 of 2 tools look like they return text written by other people but declare no untrustedContentHint, so an agent will treat the response as the site speaking.
toolsearch_rooms
search_rooms: user, rating; get_room: user, rating
fix
{ name: "search_rooms", annotations: { untrustedContentHint: true } }
passRegistration errors
2 / 2
No tool registration threw during the capture.
warningToolchange coherence
1 / 2
2 tools were registered but the page never dispatched a toolchange event, so an agent subscribed to registry updates never learns they exist.
fix
document.modelContext.dispatchEvent(new Event("toolchange"));
not applicableInjection surface
0 / 3
The injection-surface model hop returned no usable result, so tool contracts were not reviewed for injection surface.

Usefulness

100 / 100 · weight 30
passNaming quality
2 / 2
All 2 tool names are consistent, verb-led, and within Chrome's size guidance.
not applicableDescription quality
0 / 6
The description-quality model hop returned no usable result, so descriptions were not rated.
not applicableTool selection
0 / 14
The tool-selection model hop returned no usable result.
not applicableCoverage vs. site type
0 / 8
This tool set does not place the site in a category with a known expected tool shape, so there is no coverage baseline to score it against.

Human experience

0 / 100 · weight 20
warningHuman parity
0 / 8
2 of 2 tools run through the JavaScript API with no visible counterpart, so the person co-browsing cannot see what the agent is offered. Declarative forms (or at least a title annotation) close the gap.
toolsearch_rooms
search_rooms, get_room
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_rooms" tooldescription="...">
  <!-- the same action, as UI -->
</form>
not applicablePage experience
0 / 12
The page-experience model hop returned no usable result, so the page was not graded.

Tool selection

The tool-selection model hop returned no usable result.
how this was captured
chrome
148.0.7778.96
capture shim
v1
spec snapshot
2026-08
mode
fast
pages
1
tools
2
run time
10s
finished
Aug 28, 2026