Skip to main content
Glama
spliffspliff70-wq

websense

by spliffspliff70-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

page_slice

Retrieves full-fidelity records from a stored page snapshot, filtered by index, tag, role, region, or viewport for targeted inspection.

Instructions

Full-fidelity records from the stored page snapshot, filtered to ONE slice: indices / tag / role / region / vp…

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vpNotrue = in viewport only, false = off-vie…
tagNoFilter by tag, e.g. input
attrNoFilter by ANY attribute the page wrote, …
diffNoA FULL DIFF handle from a DIFF block (e.…
partNoWhich part of a cached diff (default all…
roleNo
fieldNotrue = form controls only (platform-repo…
limitNo
queryNo
tabIdNo
regionNoFilter by region substring — region is d…
frameIdNoframeId (omit=top)
indicesNoFetch exact records by inventory index —…
focusableNotrue = focusable only (el.…
interactiveNotrue = actionable only, DERIVED (focusab…

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.0.0
    • addedInput schema / properties / attr
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "properties": {
+        "name": {
+          "type": "string"
+        },
+        "value": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "name"
+      ],
+      "type": "object"
+    }
+  ],
+  "description": "Filter by ANY attribute the page wrote, …"
+}
    • addedInput schema / properties / diff
      Added value: +{
+  "description": "A FULL DIFF handle from a DIFF block (e.…",
+  "type": "string"
+}
    • addedInput schema / properties / field
      Added value: +{
+  "description": "true = form controls only (platform-repo…",
+  "type": "boolean"
+}
    • addedInput schema / properties / focusable
      Added value: +{
+  "description": "true = focusable only (el.…",
+  "type": "boolean"
+}
    • addedInput schema / properties / indices
      Added value: +{
+  "description": "Fetch exact records by inventory index —…",
+  "items": {
+    "type": "number"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / interactive / description
      Previous value: -"true = actionable elements only"New value: +"true = actionable only, DERIVED (focusab…"
    • addedInput schema / properties / part
      Added value: +{
+  "description": "Which part of a cached diff (default all…",
+  "enum": [
+    "structure",
+    "content",
+    "visual",
+    "viewport",
+    "all"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / region / description
      Previous value: -"Filter by region substring, e.g.…"New value: +"Filter by region substring — region is d…"
  2. Addedv1.4.5

TDQS

C2.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full burden. It does hint that results come from a stored snapshot rather than a live page, which is useful context, but it says nothing about whether the operation is read-only, whether snapshots must pre-exist, what happens on empty slices, pagination, or response shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no padding, which is good, but the sentence is cut off mid-enumeration ('vp…'), so its brevity stems partly from incompleteness rather than discipline. Structure is acceptable, content is not fully delivered.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter, no-required, no-annotation, no-output-schema tool, the description is far too thin. Nothing explains how the many filters combine, whether 'ONE slice' is enforced, or what the records look like, leaving major gaps an agent must guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 73%, below the high-coverage baseline, so the description should help disambiguate the 15 filters. Instead it only echoes a few slice names (indices/tag/role/region/vp) with no syntax, interaction, or precedence guidance, and truncates before finishing. It adds essentially no meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a retrieval verb and resource (full-fidelity records from a stored page snapshot), which is more than a tautology. However, it is truncated mid-sentence ('vp…') and the claim of 'filtered to ONE slice' sits uneasily against 15 independent filter parameters, leaving the actual selection model vague. It does not clearly distinguish itself from siblings like find or browse.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use, when-not-to-use, or alternative named. An agent cannot infer from the text whether this is preferred over find or browse for locating elements. Usage is only weakly implied by the phrase 'from the stored page snapshot.'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools