page_go_forwardAdvance to the next page in browser history after a back navigation. Revisit the later page without reloading the URL.
Go forward to the next page in browser history
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.7.2Output schema / oneOfPrevious value: -[
- {
- "additionalProperties": false,
- "properties": {
- "data": {
- "additionalProperties": false,
- "properties": {
- "url": {
- "type": "string"
- }
- },
- "required": [
- "url"
- ],
- "title": "PageGoForwardData",
- "type": "object"
- },
- "message": {
- "type": "string"
- },
- "ok": {
- "const": true
- }
- },
- "required": [
- "ok",
- "message",
- "data"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "data": {
- "additionalProperties": true,
- "type": "object"
- },
- "error": {
- "additionalProperties": false,
- "properties": {
- "code": {
- "type": "string"
- },
- "details": {
- "additionalProperties": true,
- "type": "object"
- },
- "message": {
- "type": "string"
- }
- },
- "required": [
- "code",
- "message"
- ],
- "type": "object"
- },
- "message": {
- "type": "string"
- },
- "ok": {
- "const": false
- }
- },
- "required": [
- "ok",
- "message",
- "error"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "additionalProperties": false,
+ "properties": {
+ "url": {
+ "title": "Url",
+ "type": "string"
+ }
+ },
+ "required": [
+ "url"
+ ],
+ "title": "PageGoForwardData",
+ "type": "object"
+ },
+ "message": {
+ "type": "string"
+ },
+ "ok": {
+ "const": true
+ }
+ },
+ "required": [
+ "ok",
+ "message",
+ "data"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "error": {
+ "additionalProperties": false,
+ "properties": {
+ "code": {
+ "type": "string"
+ },
+ "details": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "message": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "code",
+ "message"
+ ],
+ "type": "object"
+ },
+ "message": {
+ "type": "string"
+ },
+ "ok": {
+ "const": false
+ }
+ },
+ "required": [
+ "ok",
+ "message",
+ "error"
+ ],
+ "type": "object"
+ }
+]v0.5.1Input schema / descriptionPrevious value: -"Empty input schema for tools that don't require parameters."New value: +"Empty input schema for tools that don't require arguments."v0.5.0Input schema / additionalPropertiesAdded value: +falseOutput schema / additionalPropertiesRemoved value: -falsev0.4.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds minimal behavioral detail beyond the annotations, which already declare destructiveHint=true. It correctly states the action but does not elaborate on side effects or state changes.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that is front-loaded with the core action. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple parameterless tool, the description fully captures the behavior. An output schema exists, so return value information is not required in the description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and schema coverage is 100%. The description is not required to explain parameters, and the baseline score of 4 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Go forward') and resource ('next page in browser history'), clearly distinguishing it from siblings like 'page_go_back' and 'page_navigate'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implicitly states when to use (to go forward in history), but does not explicitly exclude scenarios or mention alternatives. Given the standard browser action, 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.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jumodada/Drissionpage-MCP-Server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server