Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CLAWIFI_API_KEYYesClawifi API key

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
fetchA

Fetch one URL (page or PDF) as Markdown. query returns only the top_k passages that answer it. content_scope="full" returns the whole page text. render="auto" opens the browser only for a JavaScript shell (up to 3 credits). Returns data.title, content_markdown, content_text, page_text_chars, content_chars, scope_used, language and content_status; fields: https://clawifi.dev/docs/fetch

scrapeC

Scrape a URL with source-aware routing and return structured content. formats defaults to ["markdown"]. With query, markdown and text are only the top_k passages that answer it.

search_freeA

Search the web and return ranked results: url, title, snippet, rank, provider, and published_at/modified_at when the engine gives a date. No page text; read a result with fetch. An identical search within 60 s returns cache_hit: true for 0 credits. Fields: https://clawifi.dev/docs/search

extractB

Extract structured data from a URL, with an extraction schema or a preset (or neither, for the defaults).

map_siteB

Map a site's discoverable URLs starting from a seed URL. search ranks them by relevance to a phrase.

crawlA

Start an asynchronous crawl from a seed URL. Returns a crawl_id to poll. Each page is billed; use the estimate tool first to price it.

estimateA

Price a billable call without running it or charging for it (Clawifi API 1.7.0+). operation is one of fetch, scrape, extract, map, crawl, search_free or search_content; args are that operation's fields, for example {"url": "https://example.com"}, {"seed_url": ...} for crawl or {"query": ...} for the searches. Returns estimate {minimum, maximum, raises}, balance, would_402, would_429 and binding_limit; charged is 0.

get_crawlB

Get the current status and results of a crawl.

create_jobA

Create an asynchronous job for a billable operation. Returns a job_id to poll.

get_jobB

Get the current status and results of a job.

accountA

Get the authenticated account's profile and plan.

creditsA

Get the authenticated account's credit usage and remaining balance.

list_historyA

List past requests for the authenticated account, newest first. Filters: operation (e.g. search_free), status, kind and a created_after/created_before window (ISO 8601); pass next_cursor back as cursor.

list_monitorsB

List configured Evidence Monitor checks for the authenticated account.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 14 tools

Disambiguation3/5

Three tools (fetch, scrape, extract) all retrieve content from a single URL, and only fine wording distinguishes 'Markdown of a page' from 'structured content' from 'schema-based extraction'. There is also dual async machinery (crawl/get_crawl vs create_job/get_job) plus an `estimate` tool that mirrors every other operation, so boundaries are described but easy to misselect.

Naming Consistency3/5

The set mixes consistent verb_noun names (get_crawl, create_job, get_job, map_site, list_history, list_monitors) with bare verbs (fetch, scrape, extract, crawl, estimate) and bare nouns (account, credits). It stays readable, but there is no single predictable pattern and polling is split between get_crawl and get_job.

Tool Count5/5

14 tools is comfortably within a healthy range and each maps to a plausible capability of a scraping/search API (search, fetch, scrape, extract, map, crawl, pricing, jobs, account, credits, history, monitors). Nothing is bloated enough to be unwieldy.

Completeness4/5

Core read/lifecycle workflows (search, fetch, scrape, extract, map, crawl, async jobs, cost estimation, billing, history) are well covered. Minor gaps: no cancel/delete for jobs or crawls, and list_monitors has no create/get counterpart, leaving monitor management a dead end; estimate also references a search_content operation not exposed as a tool.

Maintenance

ActivityActive
ResponsivenessNo recent community issues