Skip to main content
Glama

Tulimoa

by com.tulimoa

Submit a SaaS listing to the Tulimoa directory

submit_listing

Create a new listing in the Tulimoa directory on behalf of the authenticated user. The listing is created with status 'pending' and appears publicly only after admin review. Requires a write-scoped Tulimoa login. Use list_categories first to pick a valid category id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mcpYestrue = this tool exposes its own MCP server.
urlYesPublic homepage URL (https).
nameYesProduct/company name (max 60 chars).
tagsNoOptional descriptive tags (max 8).
countryYesISO-3166-1 alpha-2 country code of the company, e.g. DE.
categoryYesOne category id. Call list_categories for valid ids.
pricing_modelYesPricing model (required): free | freemium | paid | lifetime.
short_descriptionYesOne-line pitch (max 300 chars).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesListing id.
slugYesFinal slug (may carry a conflict suffix).
statusYes

TDQS

A4.2/5.0
Behavior4/5

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

Discloses that the listing starts as 'pending' and requires admin review before appearing publicly. Also states the need for a write-scoped login. With no annotations, this adds valuable behavioral context beyond basic creation.

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 concise sentences, each serving a distinct purpose: main action, lifecycle status, and prerequisite setup. No redundant or extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers creation, pending status, auth requirement, and prerequisite for category. Does not detail error states or rate limits, but with an output schema present, this is adequate for a creation tool.

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?

All 8 parameters are fully described in the schema (100% coverage). The description only reinforces the category parameter with a prerequisite hint. Baseline 3 is appropriate as no additional semantic detail is needed.

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?

Description clearly states the verb 'create' and resource 'listing' with context of authenticated user. It distinguishes from siblings by focusing on creation and mentions pending status, setting it apart from edit or search tools.

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?

Explicitly advises to use list_categories first for valid category IDs, which is a concrete usage hint. Lacks explicit 'when not to use' or direct comparison to edit_listing, but the guidance is strong.

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

All Tulimoa 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 has a distinct purpose: submit, edit, get, search, and list categories. No overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in lowercase with underscores, e.g., submit_listing, search_listings.

Tool Count5/5

Five tools cover the core operations of a directory server (CRUD minus delete, plus categorized search) without unnecessary bloat.

Completeness4/5

Covers create, read, update, and search. Missing delete functionality, but this may be intentional for admin-only or user unpublish actions.

Resources