KI Tools Heute

List paid add-ons (offers)

list_offers

Read-onlyIdempotent

List the optional paid add-ons a maker can buy to promote their listing (name, one-sentence effect, price in USD). Listing is always free; these only ADD reach and are always labeled 'Sponsored'. Call this to see what's purchasable before create_checkout. During free early access (early-bird), offers are not yet purchasable and this says so (purchasable=false).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`note`	Yes
`site`	Yes
`offers`	Yes
`purchasable`	Yes	False during free early access — nothing can be bought.

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description adds meaningful behavioral context: listings are free, offers only add reach, add-ons are always labeled 'Sponsored', and early-bird offerings report purchasable=false. This gives the agent a clear model of expected behavior without contradicting the 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?

The description is compact and front-loaded with the core purpose, followed by key behavioral nuances and usage context. Every sentence contributes distinct information with no redundancy or filler.

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 simple, zero-parameter read-only tool with an output schema and supportive annotations, this description is complete. It covers purpose, output contents, relation to checkout, and the special early-access condition, leaving no important gap for an agent to misuse it.

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?

With zero parameters and 100% schema coverage, the description does not need to explain inputs. It adds useful output semantics by mentioning the returned fields (name, one-sentence effect, price in USD), which compensates for the empty 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 clearly states the tool lists optional paid add-ons a maker can buy, which is a specific verb+resource combination. It distinguishes itself from create_checkout by framing this as the pre-purchase discovery step, and the title reinforces the same purpose.

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 explicitly says to call this before create_checkout, providing a clear context for use. It does not explicitly list when-not-to-use cases or mention alternative sibling tools beyond create_checkout, so it falls just short of fully explicit exclusion guidance.

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

All KI Tools Heute 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.7/5.0

Disambiguation5/5

Each tool targets a clearly distinct action: searching, retrieving details, finding alternatives, listing offers, creating a checkout, and submitting a tool. Though search_tools and list_alternatives both return catalog entries, their triggers and inputs are sufficiently different that an agent can reliably choose correctly.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: create_, get_, list_, list_, search_, submit_. The only variation is singular vs plural nouns, but the verb pattern is uniform and predictable enough that the toolset reads as one coherent convention.

Tool Count5/5

Six tools is a well-scoped size for a directory-plus-purchase workflow. Each tool covers a distinct step in the user journey, from discovery to submission to paid add-on checkout, without redundant bloat or a frustratingly thin surface.

Completeness4/5

The core workflows—search, detail retrieval, alternatives, listing creation, offer inspection, and checkout generation—are present and connect together without dead ends. However, there is no way to update, delete, or paginate through tool listings, and search_tools caps at 20 results, which is a minor gap for a full lifecycle.

Resources

Need Help?