Skip to main content
Glama
Sign In
gecko-mcp

gecko-mcp

by Frumane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_article

Read-only

Extract the main article from any web page as clean Markdown with title and byline using Readability.

Instructions

Extract the main article of a page (Readability) as clean Markdown with title and byline — great for reading content pages. Active tab unless browserId given.

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

Input Schema

NameRequiredDescriptionDefault
browserIdNoTarget tab. Defaults to active.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.4

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description adds value by specifying the output format and use of Readability algorithm. No destructive behavior is implied or contradicted.

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 purpose, second sentence clarifies parameter. No wasted words, highly efficient.

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 no output schema and low complexity (1 optional param), the description covers core functionality and output format. Could mention return value structure but sufficient for agent to use.

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?

The single parameter browserId is fully described in the schema (100% coverage) with clarification in the description about defaulting to active tab. The description adds minimal extra meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Extract' and the resource 'main article of a page', specifying output as 'clean Markdown with title and byline'. It distinguishes from siblings like read_page and snapshot by focusing on article extraction via Readability algorithm.

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 description mentions it's 'great for reading content pages' and specifies default tab behavior, but does not provide explicit when-to-use vs alternatives, nor when not to use it.

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