Skip to main content
Glama

nextsessio_read

Reads the current NextSessio page text plus numbered buttons, links, and fields, optionally scoped to one element, so an agent can inspect dashboard content.

Instructions

Read the current NextSessio page: its text and numbered buttons, links and fields.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nextsessio_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the whole burden. It does disclose the shape of what comes back (page text plus numbered interactive elements) and 'read' implies a non-mutating operation, but it never states that it is side-effect free, how numbering is assigned or reused, or whether output is truncated for large pages.

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

Conciseness4/5

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

A single front-loaded sentence with no wasted words, leading with the action and resource before the detail. It could be marginally tighter, but every clause earns its place.

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

Completeness3/5

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

For a one-parameter read tool with no output schema and no annotations, the description should explain what the returned numbering means, since that presumably connects to the click/type siblings. It describes the payload contents but leaves the linkage between element numbers and follow-up actions implicit.

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 coverage is 100% and the single 'element' parameter is already documented as 'Read only inside this element,' so the schema does the heavy lifting. The description does not mention the parameter at all or explain how scoping to an element interacts with the returned numbering, so it adds nothing beyond baseline.

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

Purpose4/5

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

The description names a specific verb (read) and resource (current NextSessio page), then enumerates what comes back: text plus numbered buttons, links and fields. That is concrete enough to tell it apart from siblings like nextsessio_click or nextsessio_type, which imply mutation, though it never explicitly contrasts with them.

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

Usage Guidelines3/5

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

Usage is only implied: reading the page is the natural precursor to clicking or typing, and the mention of 'numbered' buttons/links/fields hints that the numbers feed those actions. There is no explicit statement of when to use this versus nextsessio_status or nextsessio_guide, and no exclusion guidance.

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