Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ANTHROPIC_API_KEYNoAPI key for Anthropic, required for extract() LLM-based schema extraction

Capabilities

Features and capabilities supported by this server

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 a URL through the resilience ladder (Tier 1 static -> Tier 2 rendered, escalating only when the failure mode suggests it'll help).

Args:
    url: The URL to fetch.
    mode: "markdown" returns clean readable content (default).
          "raw" also includes the raw HTML alongside the markdown.

Returns a JSON object with the extracted content plus `confidence`,
`method` (which tier/strategy produced it), and `tier` — always
check `confidence` before trusting the result for anything important.
On failure, `failure_reason` explains why (never a silent empty result).
extractA

Fetch a URL and extract structured fields matching a caller-supplied JSON schema, using an LLM — works on ANY site, not just ones with a dedicated recipe. Use list_recipes first if you suspect a faster, higher-confidence deterministic recipe already exists for this site.

Args:
    url: The URL to extract structured data from.
    json_schema: A JSON Schema (as a JSON string) describing the fields
        to extract, e.g. '{"type":"object","properties":{"price":
        {"type":"number"},"title":{"type":"string"}}}'.
    instructions: Optional extra guidance for the extraction model.

Requires ANTHROPIC_API_KEY to be set in the environment — this tool
will return a diagnosable failure (not a crash) if it isn't.
list_recipesA

List every registered extraction recipe (platform-specific, verified parsers — e.g. Greenhouse, Lever, Ashby job boards). Check this before calling extract with a manual schema: a matching recipe is faster and higher-confidence than LLM extraction.

use_recipeA

Invoke a specific recipe by id (see list_recipes) against one entity's slug/identifier on that platform.

Args:
    recipe_id: e.g. "ats_greenhouse", "ats_lever", "ats_ashby".
    slug: The platform-specific identifier (e.g. a Greenhouse board
        token — the part of boards.greenhouse.io/<slug>).
    entity_name: A human-readable name to attach to results (e.g. the
        company name), since the raw API responses often don't include it.
health_checkB

Proactively verify a recipe or a raw URL is still working, rather than discovering breakage only when a real search silently returns zero results. Pass either a recipe id (checks with a known-good test slug isn't available generically, so this reports whether the endpoint itself is reachable and returning the expected top-level shape) or a plain URL (runs it through the ladder and reports the outcome).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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/Kaushalendra-Marcus/evident'

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