Skip to main content
Glama
jfjensen

camofox-browser MCP server (stage2)

by jfjensen

fetch_snippet

Fetch a webpage and return a short snippet from its top to quickly preview content or verify the URL before deeper analysis.

Instructions

Fetch a webpage and return a short snippet from the top of it.

This is the quick-look tool. It returns the head of the page's accessibility-tree snapshot, which is usually enough to tell what the page is and whether it is the right one. If the page is longer than the snippet, the result ends with a marker telling you to use summarize for the full content or extract for specific fields.

Use this when you want a fast look at a page, or to confirm a URL is what you expect before doing more with it. For a full understanding of a long page, prefer summarize; for named fields, prefer extract.

Args: url: The full URL to fetch (must include http:// or https://). user_id: Optional. If set, camofox reuses a browser context across calls (faster). Default opens a one-shot tab.

Returns: The head of the page snapshot, with a marker if it was longer.

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?

No annotations, but the description discloses that the result includes a marker if the page is longer, and explains the user_id parameter's effect on browser context reuse, adding behavioral context beyond schema.

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?

The description is concise, well-structured with intro, output explanation, usage guidance, and parameter details, no wasted sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with an output schema, the description adequately explains purpose, output, and parameters, making it complete for correct invocation.

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?

Schema description coverage is 0%, but the description adds meaning: URL must include http:// or https://, and user_id is optional with context reuse behavior explained.

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 a short snippet from the top, explicitly differentiating it from siblings like 'summarize' and 'extract' for full content or specific fields.

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?

The description explicitly states when to use it (fast look, confirm URL) and when not to (prefer 'summarize' for full content, 'extract' for named fields), providing clear guidance over alternatives.

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