Skip to main content
Glama

Disco

by com.leap-labs

discovery_signup

Idempotent

Create a Disco account and get an API key.

Provide an email address to start the signup flow. If email verification
is required, returns {"status": "verification_required"} — the user will
receive a 6-digit code by email, then call discovery_signup_verify to
complete signup and receive the API key. The free tier (10 credits/month,
unlimited public runs) is active immediately. No authentication required.

Returns 409 if the email is already registered.

Args:
    email: Email address for the new account.
    name: Display name (optional — defaults to email local part).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
emailYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.7/5.0
Behavior5/5

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

The description goes well beyond the annotations (idempotentHint, destructiveHint) by disclosing key behaviors: returns verification_required with a 6-digit code, free tier activation, 409 for existing email, and no authentication required. This provides rich context about what happens during the signup flow, including the two-step process and error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded with the main purpose. It uses a clear structure: one-sentence summary, flow explanation, notes, and parameter list. While slightly longer than minimal, every sentence adds necessary detail for correct invocation.

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?

For a signup tool with a two-step flow, the description thoroughly covers the complete lifecycle: initial request, verification requirement, next step (discovery_signup_verify), free tier behavior, auth requirement, and error condition (409). It is comprehensive enough for an agent to know what to expect and how to proceed.

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?

With 0% schema_description_coverage, the description fully compensates by explaining both parameters: 'email: Email address for the new account' and 'name: Display name (optional — defaults to email local part)'. It adds important semantics like optionality and default behavior not present in the schema.

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?

The description explicitly states 'Create a Disco account and get an API key', using a specific verb and resource. It clearly distinguishes itself from sibling tools like discovery_login and discovery_signup_verify by describing the signup flow and pointing to the verification step.

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

Usage Guidelines4/5

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

The description provides clear when-to-use guidance by describing the signup flow and directing users to call discovery_signup_verify after verification. It also implies when not to use (e.g., when email is already registered, a 409 is returned, suggesting login instead). However, it does not explicitly name alternative tools or state when to use them, only implicitly differentiating via the flow.

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