Skip to main content
Glama
jfjensen

camofox-browser MCP server (stage2)

by jfjensen

fetch_structure

Extract a webpage's heading outline to see its structure and find relevant sections before reading the full page.

Instructions

Fetch a webpage and return its heading outline: the page's headings with their levels, in order, like a table of contents.

Use this to see how a page is organized and whether the section you want is on it, before deciding what to read in full. Note that some pages (short stubs, pages whose content sits in tables or infoboxes rather than under headings) have a thin outline; in that case prefer summarize or extract.

Args: url: The full URL to outline. user_id: Optional, same semantics as for fetch_snippet.

Returns: A plain-text outline, one heading per line, indented by level.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
user_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses return format (plain-text outline indented by level) and notes pages with thin outlines. Lacks details on side effects or auth requirements, but overall informative.

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?

Concise, well-structured description: purpose, usage, then arguments. Every sentence adds value.

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?

Covers purpose, usage, and return format adequately. Could mention if full page is read, but sufficient for a simple tool.

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?

Explains 'url' as 'The full URL to outline' and 'user_id' as optional with same semantics as fetch_snippet. Adds meaning but user_id relies on external reference.

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 it fetches a webpage and returns its heading outline, like a table of contents. It distinguishes from sibling tools like 'summarize' and 'extract'.

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

Usage Guidelines5/5

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

Explicitly tells when to use (to see page organization before reading) and when not to (thin outlines, then prefer 'summarize' or 'extract').

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jfjensen/local-LLM-agent-mcp-interaction'

If you have feedback or need assistance with the MCP directory API, please join our Discord server