Beste KI Tools

Submit a new AI tool

submit_tool

Submit a new AI tool to Beste KI Tools on behalf of its maker. Creates a draft listing (not yet public) and returns a claimUrl the maker must visit to sign up and claim/publish it. Call this only when a user explicitly wants to list their own tool — never to submit a tool on someone else's behalf without their email. Rate-limited globally to 5 submissions per hour. Supply tagline, problemSolved, logoUrl and imageUrls whenever you can: they are what make the published listing look like a real product page rather than a stub.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	The tool's https homepage URL.
`name`	Yes	The tool's name.
`email`	Yes	The maker's email — used to claim the listing on signup.
`logoUrl`	No	https URL of the tool's logo. We copy it to our own storage — we never hotlink the maker's host.
`tagline`	No	One line shown on every card (max 60 chars). Supply it — without one we fall back to a truncated description.
`xHandle`	No	X/Twitter handle, without the @.
`category`	Yes	Category slug, e.g. 'agents', 'writing', 'coding', 'design', 'marketing', 'productivity', 'video', 'analytics'.
`imageUrls`	No	Up to 5 https screenshot URLs, best first. Copied to our own storage. Without any, the listing shows a generated placeholder card instead of a real screenshot.
`description`	Yes	A description of the tool (40-1000 chars).
`problemSolved`	No	What problem the tool solves, in the maker's words (max 160 chars). Rendered as its own block on the listing page.
`xHandleIsFounder`	No	True when the handle is the founder's personal account rather than the product's.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`error`	No
`claimUrl`	No	Where the maker signs up to claim the DRAFT. Present only when ok is true.

TDQS

A4.9/5.0

Behavior5/5

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

The description adds substantial behavioral detail beyond annotations: listings are drafts, not public; a claimUrl is returned; the tool is globally rate-limited to 5 submissions per hour; logo/image URLs are copied to storage. This gives the agent important operational expectations not conveyed by the readOnlyHint/idempotentHint/destructiveHint flags.

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-loaded with the core purpose and result, followed by usage constraints and field guidance. No filler or repetition; every sentence adds value.

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 tool with 11 parameters and an output schema, the description covers the most decision-critical context: draft vs public state, claim flow, rate limit, ownership/consent rule, and the role of optional fields. It is complete enough for an agent to invoke correctly without further documentation.

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 already 100%, so the baseline is 3. The description adds meaningful parameter guidance by emphasizing tagline, problemSolved, logoUrl, and imageUrls, explaining why they matter, and noting fallback behavior (e.g., truncated description, placeholder card) that is not in the schema itself.

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 states a specific action ('Submit a new AI tool to Beste KI Tools on behalf of its maker') and the concrete result ('Creates a draft listing... returns a claimUrl'). It clearly differentiates this tool from read/list/search siblings by describing the submission and claimed-publish workflow.

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?

Explicit when-to-use guidance is provided: 'Call this only when a user explicitly wants to list their own tool.' It also states a boundary condition ('never to submit a tool on someone else's behalf without their email'), which helps the agent avoid misuse despite there being no sibling tool with overlapping submission behavior.

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

All Beste KI Tools 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 has a clear, distinct purpose: search for discovery, get for details, list alternatives for comparison, list offers for add-ons, create checkout for purchasing, and submit for adding new tools. No overlapping functionality is apparent.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case, with clear verbs like create, get, list, search, and submit. The naming is uniform and intuitive.

Tool Count5/5

With six tools, the set is appropriately sized for a catalog server covering search, retrieval, submission, and purchase flows. It's neither sparse nor bloated.

Completeness5/5

The tool surface covers the key user journeys: discovering tools (search, get, list alternatives), purchasing add-ons (list offers, create checkout), and contributing (submit). No essential operation seems missing for the stated purpose.

Resources

Need Help?