Skip to main content
Glama
Sign In
Browser Control

Browser Control

by PrinceGarth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get-recent-browser-history

Retrieve recent Firefox browsing history to review visited sites. Optionally filter by search query to find specific entries.

Instructions

Get the list of recent browser history (to get all, don't use searchQuery)

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": "get-recent-browser-history"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchQueryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/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 not disclose what 'recent' means (time window, count limit), the return shape, ordering, or any permission requirements. Only the filtering hint is given.

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 waste. The parenthetical is compact, though slightly awkwardly placed at the end.

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?

With no output schema and no annotations, the description leaves important details unspecified: what a history entry contains, how many results return, and how recency is bounded. Adequate for selection but not for confident invocation.

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 0% for the single searchQuery parameter, so the description must compensate. It only indicates that omitting searchQuery returns everything, which conveys the filter's effect but not its matching semantics, format, or scope.

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 clear verb+resource: 'Get the list of recent browser history'. An agent can tell it retrieves history rather than tab state. However, it does not differentiate itself from the sibling tab-oriented tools or clarify scope of 'recent'.

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?

The parenthetical 'to get all, don't use searchQuery' implies the searchQuery parameter filters results, which is implicit usage guidance. There is no statement of when to prefer this tool over siblings or any prerequisites/exclusions.

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