asksteps

asksteps: what it does, what it costs

asksteps_get_capabilities

Read-onlyIdempotent

Returns what asksteps is, its bookable plans with net prices, and what every quota key means. Call this FIRST when you are asked whether asksteps fits a use case, what it costs, or before you create anything — it answers plan, price and limit questions in a single call. Prices are net and the returned vatNote states how to treat them; do not compute gross prices without it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`locale`	No	Preferred language for the product description, as an ISO 639-1 code such as "de" or "en". Defaults to German.

Output Schema

TableJSON Schema

Name	Required	Description
`plans`	Yes	Publicly bookable plans with net prices and their quotas. Prices are NET (excluding VAT).
`quotas`	Yes	What each quota key in the plans means.
`product`	Yes	The product name.
`summary`	Yes	One-paragraph description of what asksteps does, taken verbatim from the product's own home page.
`vatNote`	Yes	VAT note for the listed prices. Do not compute gross prices without honouring this.
`website`	Yes	Canonical base URL of the product website.
`nextSteps`	Yes	Suggested next tool calls or URLs, in the order that usually makes sense.

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already indicate a safe, idempotent read operation. The description adds meaningful behavioral context: prices are net, the vatNote field controls how they should be treated, and gross prices should not be computed without it. This goes beyond the structured 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?

Three sentences front-load the core purpose, then provide usage timing and a critical pricing caveat. There is no filler and each sentence contributes essential guidance.

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?

An output schema exists, so return values are covered. The description supplies the missing context: when to invoke this first, what it answers in one call, and how to handle the vatNote and net prices. For a simple one-parameter discovery tool, nothing essential is missing.

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?

There is only one optional parameter, locale, and the input schema already documents it fully with an example and default. The description does not need to add parameter-level detail, so the baseline of 3 applies.

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 clearly states what the tool returns: asksteps overview, bookable plans with net prices, and quota key meanings. It names a specific verb and resource, and it distinguishes itself from the sibling tools by being the planning/information endpoint rather than a CRUD or workflow tool.

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 gives explicit 'call this FIRST' guidance and specifies the triggering questions: whether asksteps fits a use case, what it costs, or before creating anything. It does not name alternative tools or give when-not-to-use conditions, but the context is clear enough for an agent to route correctly.

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

All asksteps tools Inspect

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.3/5.0

Disambiguation4/5

Tools are mostly distinct with clear ownership of each resource and action, and descriptions explicitly contrast sibling pairs (analyze_pdf vs import_pdf, create_form vs create_funnel, publish_form vs update_publication, change_plan vs start_checkout). However, an agent skimming names alone could misselect between the four creation tools or the two PDF tools without reading the descriptions carefully.

Naming Consistency5/5

Every tool follows the asksteps_<verb>_<noun> pattern perfectly, with uniform verbs like get_, list_, create_, and update_. The only slight deviation is create_from_template, but even that stays predictable and readable within the convention.

Tool Count3/5

At 24 tools, this sits at the heavy end of the 16-25 borderline range. The broad domain (form/funnel building, publishing, PDF import, billing, stats, leads) justifies most of them and there is no obvious redundancy, but the sheer volume makes navigation harder than a tighter set.

Completeness4/5

The core form and funnel lifecycle is well covered: multiple creation paths, read, full replacement update, delete with confirmation, publish/unpublish, stats, and leads export. Billing covers first purchase, plan changes, and quota checks. Minor gaps exist — no dedicated subdomain listing tool, no funnel-specific stats, and no programmatic PDF field mapping — but these are explicitly documented as human steps, so agents can work around them.

Resources

Need Help?