Skip to main content
Glama
habibafaisal

wherewent

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
analyze_jobA

Run a Python/SQLAlchemy job under wherewent and return WHY it was slow.

    Use when a batch job is slow and you need the exact call site, query
    count, and fix — wherewent counts/groups/attributes deterministically in
    Python (zero token cost) and hands back machine fields to act on.

    Args:
        command: The job as an argv LIST, e.g. ["python", "job.py"] or
            ["python", "-m", "mypkg"]. TRUST BOUNDARY: this list is executed
            directly with NO shell (no shell=True) — no interpolation, no
            injection. The agent platform's sandbox is the outer boundary.
        unit_function: Optional SPEC (e.g. "myapp.jobs:process_receivable")
            to enable per-unit trend analysis (rising per-unit cost).
        timeout_s: Max seconds to let the job run (default 600). Real jobs can
            run for hours — on timeout the child is stopped and PARTIAL
            results are returned with timed_out=True. Partial data is a
            first-class use: read the per-unit growth trend.

    Returns an envelope: {"result": <enriched wherewent JSON or null>,
    "exit_code", "timed_out", "stderr_tail", "error"}. Each finding in
    result.findings carries fix/call_site/calls/evidence. Act on `fix`; cite
    `call_site` + `evidence`.
    
explain_runA

Return the enriched analysis from a saved wherewent JSON file.

    For the "job already ran under `wherewent run --save out.json`" case —
    no re-run. Returns the same enriched schema analyze_job produces, with
    each finding carrying fix/call_site/calls/evidence.

    Args:
        path: Path to a JSON file written by `wherewent run --save`.
    

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/habibafaisal/wherewent'

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