Skip to main content
Glama
Sign In
mya11yreport-mcp

mya11yreport-mcp

by mya11yreport
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get scroll position

get_scroll_position

Retrieve scroll position, document dimensions, and viewport size to compute scroll_by deltas for navigation.

Instructions

Returns the current scroll position of the session page plus document scroll dimensions and the viewport size — useful for planning further scroll_by deltas.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sessionId": "<sessionId>"
    },
    "name": "get_scroll_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesSession id returned by start_session. Required on every stateful tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that the tool returns scroll position, document scroll dimensions, and viewport size, which is helpful. However, it doesn't mention whether this is a read-only operation, any side effects, or what the exact return shape is. Since it's a getter, the read-only nature is implied but not explicit.

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

Conciseness5/5

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

One sentence, front-loaded with the main purpose, and the use-case hint is appended. No wasted words.

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

Completeness4/5

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

For a simple getter with one parameter and no output schema, the description is mostly complete. It could mention that the return values are in pixels or that it's read-only, but the core information an agent needs to call it correctly is present.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents the sessionId parameter. The description doesn't add any parameter-specific meaning beyond what the schema provides, which is fine given the high coverage.

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

Purpose5/5

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

The description states a specific verb ('Returns') and resource ('current scroll position of the session page') and adds the extra dimensions and viewport size. It clearly distinguishes itself from get_viewport_size and scroll_by, which are siblings.

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

Usage Guidelines4/5

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

The description says it is 'useful for planning further scroll_by deltas', which gives clear context for when to use it. It doesn't explicitly mention when not to use it or name alternatives like get_viewport_size, but the context is clear enough.

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