lyra-browser

Official

by Intrect-io

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_url

Retrieve the current page URL, title, and open tab count to track browsing context and verify navigation state.

Instructions

Return the current URL and page title, and how many tabs are open (tab_count).

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 3, 2026

TDQS

A3.5/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 burden. It does disclose the returned fields (URL, title, tab_count), which implies a side-effect-free read, but it says nothing about permissions, freshness, or behavior on non-page contexts (e.g. no tabs open).

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?

A single front-loaded sentence with zero filler. Every clause maps to a distinct returned value; nothing needs trimming.

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?

Given zero parameters and an existing output schema, the description need not explain return structure, and the tool is simple enough that little more is required. The only gap is its unstated relationship to the overlapping 'tabs' sibling.

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 the schema imposes no documentation burden and the baseline of 4 applies. The mention of the 'tab_count' field is descriptive of output, not a parameter.

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 ('Return') and precise resources: current URL, page title, and open tab count. The scope is unambiguous, though it never distinguishes itself from the sibling 'tabs' tool, which plausibly reports similar tab information.

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

Usage Guidelines2/5

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

Purely descriptive with no when-to-use guidance, prerequisites, or alternatives. An agent gets no help deciding between get_url, tabs, or read_page for retrieving page context.

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