Skip to main content
Glama

Open the Portward page

open_page
Read-only

Opens the local Portward page in the user's browser so they can view and manage history, saved pulls, block rules, settings, and AI-sent data.

Instructions

Open the user's Portward page in their web browser, on this computer: their history, saved pulls, block rules, settings and what the AI was sent. Call it when the user asks to see or manage those. The page opens for the user; you aren't given its address.

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": "open_page"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: the page opens for the user on their own computer, and the agent is not given the address — telling the agent not to expect a URL or content back. It doesn't say what happens if the browser is already open or if opening fails, but the essential behavioral expectation is set.

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?

Two sentences, front-loaded with the action, then the trigger condition and the key caveat about not receiving the address. No filler, no repetition of the title.

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 zero-parameter, no-output-schema tool, the description covers the action, the trigger, and the expectation that no address is returned. Minor gaps remain — whether it reuses an already-open window and what the agent should tell the user afterward — but nothing needed to call it correctly is missing.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline of 4 applies; no parameter surface is left unexplained.

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?

States a specific verb and resource ("Open the user's Portward page in their web browser, on this computer") and enumerates what the page contains (history, saved pulls, block rules, settings, AI log). That places it clearly as a UI-opening action rather than a data-returning one, though it doesn't explicitly distinguish it from siblings like history or list_rules that seem to cover similar subject matter.

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?

"Call it when the user asks to see or manage those" gives an implied trigger condition tied to the listed page areas. There are no exclusions, no prerequisites, and no named alternative for cases where the user just wants the underlying data rather than the page, so the agent must infer the boundary.

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