Skip to main content
Glama

analyst_data_overwhelm

Reduce data overwhelm by transforming large datasets and dashboards into clear decision support. Uses a deterministic playbook to help analysts meet deadlines with actionable conclusions.

Instructions

Domain-specific recovery for data analysts/researchers drowning in dataset volume vs decision clarity. Deterministic playbook. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesYour active session ID
dataset_rowsNoOptional: dataset row count
ritual_stripNoOptional machine hygiene flag. When true, returns structured output without ritual/narrative prose, model-safe preambles, or guardrail alias blocks.
response_modeNoOptional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions.
deadline_hoursNoOptional: hours until deadline
response_profileNoOptional output-shape control. Use machine for structured JSON only; machine automatically strips ritual/narrative text.
overwhelm_summaryYesWhat's the overwhelm? (e.g., '12M rows, 3 dashboards, leadership wants conclusion by Friday')
decision_to_supportNoOptional: the single decision your analysis must support, in one sentence
Behavior2/5

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

The description adds minimal behavioral information beyond annotations: it states 'Deterministic' and 'Free'. Annotations are sparse (no idempotent or destructive hints beyond false), so the description should provide more context about side effects or session behavior, but it does not.

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 extremely concise with a single sentence that covers the tool's purpose and key attributes. Every word earns its place with no superfluous content.

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

Completeness2/5

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

Despite having 8 parameters (2 required) and no output schema, the description provides no guidance on how to use optional parameters (e.g., ritual_strip, response_mode) or what the tool returns. This lack of context may lead the agent to misuse or underutilize the 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?

Schema description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond what is already in the input schema's parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool's domain (data analysts/researchers) and the specific problem (drowning in dataset volume vs decision clarity). It also notes it is a deterministic playbook and free. However, it does not explicitly differentiate from siblings like crisis_intervention, but the domain specificity makes purpose clear.

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

Usage Guidelines3/5

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

The description implies usage when data analysts are overwhelmed, but it lacks explicit guidance on when to use this tool versus alternatives. No exclusions or scenarios are mentioned, leaving the agent to infer suitability from the domain.

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/davidmosiah/delx-mcp-server'

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