gritworks.ai WebMCP audit

Name: gritworks.ai WebMCP audit
Creator: ora

Rescan

audited Sep 2, 2026in 12s

82/ 100100% of the applicable check weight evaluated

6 tools registered. Strongest in task completion, weakest in trust.

Shared experience75

Task completion100

Tool quality91

Trust60

https://gritworks.ai

Tools

6 read, 0 write

Loading map

gritworks_overview

What GritWorks does, how GritRedact and GritRender divide the work, and where the software runs. Use before recommending or describing GritWorks.Answers a question. Declared read only.

pagehttps://gritworks.ai/

implementation

viaimperative

entry pointdocument

registered after786ms

executepresent

api surfaceTakes no parameters.

annotations

read onlytrue

untrusted contentnot declared

titlenot declared

2 findings

warningNaming quality

weight 2

Tool naming makes selection harder than it needs to be: 6 names do not start with a verb (gritworks_overview).

fix

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

warningInjection surface

weight 4

2 of 6 tools carry instruction-shaped text in their own metadata: gritworks_overview Description instructs agent when to use the tool..

gritworks_overview: Description instructs agent when to use the tool.; gritworks_list_pages: Description instructs agent when to use the tool.

fix

{
  name: "gritworks_overview",
  // Metadata DESCRIBES the tool - it never addresses the agent reading it.
  // Rewrite any name, description, title, or schema field description that
  // instructs the agent (which tool to prefer, what to output, rules to
  // ignore) so it states what the tool does and what it returns instead.
  description: "Searches the catalog and returns matching items with prices."
}

tool json

{
  "name": "gritworks_overview",
  "description": "What GritWorks does, how GritRedact and GritRender divide the work, and where the software runs. Use before recommending or describing GritWorks.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Findings

Shared experience

75 / 100 · weight 30

warningPage experience

weight 20

1 of 4 page-experience marks came back short: readability The main text is very light and hard to read against the white background..

readability: poor

warningHuman parity

weight 10

The page the person sees came back short of the agent surface (1 of 4 page-experience marks came back short: readability The main text is very light and hard to read against the wh...), so the two are not sharing an equal experience.

fix

// Make the tool's effect visible on the page the person is looking at:
// update the same UI your existing human flow uses when your_tool_name runs,
// so the person co-browsing sees what the agent just did.
execute: async (args, { signal }) => {
  const result = await performAction(args, signal);
  renderResultInPage(result); // the human-visible half of the same action
  return result;
}

Task completion

100 / 100 · weight 25

passTool selection

weight 15

An agent chose an existing, callable tool and built a schema-valid call for all 1 canonical intents, each matching the kind of tool its intent needs. Nothing was executed, so this verifies selection, not outcomes.

not applicableCoverage vs. site type

weight 10

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.

Tool quality

91 / 100 · weight 25

passRegistration timing

weight 1

Every measured tool registered within 786ms of navigation.

toolgritworks_check_fit

passCanonical entry point

weight 3

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

passSchema validity

weight 4

All 6 declared input schemas are structurally valid object schemas.

warningSchema quality

weight 4

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

toolgritworks_case_studies

gritworks_case_studies: declares no required list, so an agent cannot tell which parameters are mandatory; gritworks_list_pages: declares no required list, so an agent cannot tell which parameters are

fix

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

warningNaming quality

weight 2

Tool naming makes selection harder than it needs to be: 6 names do not start with a verb (gritworks_overview).

toolgritworks_overview

fix

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

passStub detection

weight 4

All 6 tools declare an execute handler.

passRegistration errors

weight 2

No tool registration threw during the capture.

passDescription quality

weight 5

All 6 rated tool descriptions say what the tool does, when to use it, and what it returns.

Trust

60 / 100 · weight 20

not applicableAnnotations present

weight 6

No tool name reads like a read, and an absent readOnlyHint already defaults to "this may write" - the one hint worth declaring here is readOnlyHint: true on read tools, and this set has none to declare it on.

passAnnotation mismatch

weight 6

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

not applicableUntrusted content hint

weight 4

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

warningInjection surface

weight 4

2 of 6 tools carry instruction-shaped text in their own metadata: gritworks_overview Description instructs agent when to use the tool..

toolgritworks_overview

gritworks_overview: Description instructs agent when to use the tool.; gritworks_list_pages: Description instructs agent when to use the tool.

fix

{
  name: "gritworks_overview",
  // Metadata DESCRIBES the tool - it never addresses the agent reading it.
  // Rewrite any name, description, title, or schema field description that
  // instructs the agent (which tool to prefer, what to output, rules to
  // ignore) so it states what the tool does and what it returns instead.
  description: "Searches the catalog and returns matching items with prices."
}

Tool selection

100% across 1 intents

I want to gritworks overview on this site.ok

chosegritworks_overviewexpected gritworks overviewkind matched

arguments

{}

model: gemini-2.5-flash

Add the tools this site is missing

Our scanner reads your website and suggests the right WebMCP tools for it.

The open source webmcp plugin teaches your coding agent to audit a site, implement tools on document.modelContext, and verify them in a real browser. npx @ora-ai/webmcp-verify runs the verification on its own. No signup, no hosted service.

how this was captured

observed via: capture shim (Chromium 148.0.7778.96)
chrome: 148.0.7778.96
capture shim: v2
spec snapshot: 2026-08-26
mode: fast
pages: 1 - entry page only
tools: 6
run time: 12s
finished: Sep 2, 2026

Checked the way in-browser agents discover tools: the top-level document's modelContext registry, read after the page settles.