Skip to main content
Glama

Disco

by com.leap-labs

discovery_estimate

Read-only

Estimate the credits required to run a Disco analysis.

Returns `required_credits` for public (always 0) and private, with private
split by whether LLMs are enabled (use_llms=False is faster, use_llms=True
adds smarter preprocessing, literature context and a written summary).
Also returns per-visibility depth caps and accepted file formats. No
authentication required — when an API key is supplied, also returns the
caller's available credits.

Call this before discovery_analyze whenever cost or feasibility is unclear.

Args:
    file_size_mb: Size of the dataset in megabytes.
    num_columns: Number of columns in the dataset.
    analysis_depth: Search depth (1=fast, higher=deeper). Used to compute the
        private-run cost. Default 2.
    api_key: Disco API key (disco_...). Optional. When provided, the response
        includes `account.available_credits`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNo
num_columnsYes
file_size_mbYes
analysis_depthNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A5/5.0
Behavior5/5

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

Provides extensive behavioral details beyond the readOnlyHint annotation: public analyses always cost 0, private costs split by LLM usage, and response includes depth caps and file formats. Also explains optional API key behavior and available credits. No contradiction with annotations.

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?

Well-structured with a clear opening, bullet-like details, and an Args list. Every sentence adds value, and the description is appropriately sized for the tool's complexity.

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?

Comprehensive for a pre-flight estimation tool: describes return values, explains cost logic, provides usage context, and covers all parameters. Output schema exists but the description already echoes key return fields, making it self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions are absent, but the Args section thoroughly explains each parameter (file_size_mb, num_columns, analysis_depth, api_key) including defaults and effects on the estimate. Fully compensates for schema gaps.

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?

Clearly states 'Estimate the credits required to run a Disco analysis' with a specific verb and resource. Distinguishes from sibling tools like discovery_analyze, which actually runs the analysis.

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?

Explicitly instructs to call before discovery_analyze when cost or feasibility is unclear, and clarifies authentication requirements. Names the related tool and provides clear when-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Disco toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct operation (account, payment, analysis, plans, login flows, etc.) with no overlap. Even paired tools like signup/login and their verify counterparts are clearly differentiated.

Naming Consistency5/5

All tools follow a consistent 'discovery_' prefix + verb_noun pattern (e.g., discovery_add_payment_method, discovery_get_results). No mixed conventions or vague names.

Tool Count5/5

14 tools cover account management, analysis pipeline, and billing without unnecessary redundancy. The scope is well-matched to the server's purpose.

Completeness4/5

The tool set covers the full user journey from signup and payment to running analyses and retrieving results. Minor gaps exist (e.g., no explicit cancellation of subscriptions), but the core workflow is fully supported.

Resources