Skip to main content
Glama

DECA Labs

Price a demand test

quote_test
Read-only

The price of testing an idea with ten days of real ads, before anything is paid. You pay only the ad budget, at cost, in USDC on Base; there is no fee. The budget is sized to the idea: several options (signal, clear read, market comparison, or your own budget), each with its expected visits, the number of confirmed sign-ups it must reach to pass, and what it can and cannot tell. Use an idea_id from get_ideas or describe your own idea. The quote is valid for 30 minutes. Free; nothing is charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "quote_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
ideaNoYour own idea, when it is not from get_ideas. It is never published.
idea_idNoAn idea's id from get_ideas.
marketsNoWhere the ads run. Default: US, GB, CA.
budget_usdNoA budget of your own to price alongside the options, between 250 and 2000. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses the cost model (pay only ad budget at cost in USDC on Base, no fee), quote expiry of 30 minutes, and that no charge occurs at quote time. It also explains the shape of the response — multiple budget options each with expected visits, the confirmed sign-up threshold to pass, and what each can and cannot tell — which is context the annotations cannot provide.

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 front-loaded with the core definition and organized from what the tool is, to how pricing works, to inputs, to validity. The closing line 'Free; nothing is charged' is somewhat redundant with the earlier 'before anything is paid' and 'there is no fee', which is the only real waste.

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?

Although there is no output schema, the description explains what the quote contains (options, expected visits, pass thresholds, interpretive limits) and the validity window, so an agent can both call it and reason about the result. Nothing essential for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it ties idea_id to get_ideas, clarifies that a self-described idea is an alternative to a stored one, and frames budget_usd as an additional option priced alongside the generated tiers rather than a required input.

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 opens with a specific verb-and-resource pairing: pricing a demand test built from ten days of real ads. It makes clear this is a quoting step, not a start/execution step, which separates it from siblings like start_test and get_test without relying on their names.

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?

It gives explicit input sourcing guidance ('Use an idea_id from get_ideas or describe your own idea'), which tells the agent which branch of the schema to use and when. It stops short of an explicit sequencing statement such as calling this before start_test, so it is strong but not fully prescriptive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources