Skip to main content
Glama

nextsessio_guide

Call this first to navigate NextSessio for reviewing bookings, tracking prepaid package balances, verifying visits, and locating screens and the sign-in link.

Instructions

How to work in NextSessio (review bookings, track prepaid package balances and verify visits): its screens and the sign-in link. Call this first.

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_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in NextSessio, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/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 full behavioral burden. It does disclose the informational content (screens and a sign-in link), which implies a read-only, non-mutating step, but it never says whether the tool touches the target app, whether it needs an active session, or how large/fresh the returned guidance is. Adequate but thin for a no-annotation tool.

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?

One compact sentence plus a front-loaded directive: the domain, the payload, and the call ordering all land before any filler. The parenthetical list is dense but earns its place by scoping the tool's coverage.

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 low-complexity, zero-output-schema orientation tool, the description covers what the tool provides but not how it connects to the six sibling interaction primitives or what the agent should do with the returned screens and sign-in link. A closing sentence on that hand-off would make it complete.

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?

There is a single optional parameter with 100% schema coverage, so the baseline is 3. The description adds no meaning beyond the schema's own phrasing about describing the desired task, and it does not indicate how a vague or empty task value affects the guidance returned.

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 the specific target (NextSessio) and enumerates the concrete domains it covers: review bookings, prepaid package balances, verify visits, plus screens and the sign-in link. That distinguishes it from the sibling primitives (click/open/type/read/close), which are generic interaction verbs. It falls short of 5 only because it never states the output form (instructions/markdown/URL list) explicitly.

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?

"Call this first" is an explicit sequencing rule that tells an agent exactly when this tool takes precedence over its siblings. There is no stated exclusion or follow-up path, so an agent still has to infer what to do after reading the guide and when the guide is unnecessary.

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