latitude.so WebMCP audit

Name: latitude.so WebMCP audit
Creator: ora

Rescan

audited Aug 28, 2026in 6s

68/ 100

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

WebMCP use76

Usefulness98

Human experience0

about:blank

No agent run recorded yet.

No steps recorded

Tools

navigate_to

Navigate the browser to a key Latitude page such as pricing, blog, changelog, documentation, signup, or book-demo.Takes an action on the site.

pagehttps://latitude.so/

implementation

viaimperative

entry pointdocument

registered after413ms

executepresent

api surface

pagerequired

annotations

read onlynot declared

destructivenot declared

idempotentnot declared

open worldnot declared

untrusted contentnot declared

titlenot declared

3 findings

warningNaming quality

1.8 / 2

Tool naming makes selection harder than it needs to be: 1 name does not start with a verb (navigate_to).

fix

{ name: "navigate_to" /* short, unique, verb-based */ }

warningAnnotations present

3.2 / 4

1 of 5 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.

navigate_to

fix

{
  name: "navigate_to",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}

warningHuman parity

0 / 8

5 of 5 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.

navigate_to, get_site_pages, get_page_context, search_blog, list_changelog

fix

<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="navigate_to" tooldescription="...">
  <!-- the same action, as UI -->
</form>

tool json

{
  "name": "navigate_to",
  "description": "Navigate the browser to a key Latitude page such as pricing, blog, changelog, documentation, signup, or book-demo.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "page": {
        "type": "string",
        "enum": [
          "home",
          "pricing",
          "blog",
          "changelog",
          "about",
          "privacy",
          "terms",
          "book-demo",
          "signup",
          "docs",
          "github"
        ],
        "description": "Destination page key."
      }
    },
    "required": [
      "page"
    ]
  },
  "annotations": {}
}

Findings

WebMCP use

76 / 100 · weight 50

passTools registered

4 / 4

5 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.

passRegistration timing

4 / 4

Every measured tool registered within 412.69999980926514ms of navigation.

toollist_changelog

passCanonical entry point

4 / 4

All 5 tools register on the canonical document.modelContext entry point.

passSchema validity

5 / 5

All 5 tools declare a structurally valid object input schema.

warningSchema quality

3.2 / 4

1 of 5 tool schemas are harder for an agent to use than they need to be: list_changelog declares no required list, so an agent cannot tell which parameters are mandatory.

toollist_changelog

list_changelog: declares no required list, so an agent cannot tell which parameters are mandatory

fix

{
  name: "list_changelog",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}

passStub detection

5 / 5

All 5 tools declare an execute handler.

warningAnnotations present

3.2 / 4

1 of 5 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.

toolnavigate_to

navigate_to

fix

{
  name: "navigate_to",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}

passAnnotation mismatch

3 / 3

No tool claims to be read-only while its name says it writes (4 declared hints checked).

not applicableUntrusted content hint

0 / 2

No tool's contract suggests it returns text written by somebody other than the site, so there is nothing to flag as untrusted.

passRegistration errors

2 / 2

No tool registration threw during the capture.

warningToolchange coherence

1 / 2

5 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

98 / 100 · weight 30

warningNaming quality

1.8 / 2

Tool naming makes selection harder than it needs to be: 1 name does not start with a verb (navigate_to).

toolnavigate_to

fix

{ name: "navigate_to" /* short, unique, verb-based */ }

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.

passCoverage vs. site type

8 / 8

The tool set covers the whole core docs flow: search or browse the catalog, read a page or article, navigate the documentation tree.

Human experience

0 / 100 · weight 20

warningHuman parity

0 / 8

toolnavigate_to

navigate_to, get_site_pages, get_page_context, search_blog, list_changelog

fix

<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="navigate_to" 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: 5
run time: 6s
finished: Aug 28, 2026