Capability tiers available on Defici, described by what each tier unlocks — not by price (pricing is not finalized yet, so no price figure is returned by this tool). Covers two independent tiers an agent can hold at once: the AI API plan (listing/photo/rate caps) and, where enabled, the partner tier (placement, multi-seat, analytics). Only capabilities that are live today are listed here.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It helpful states that no price figure is returned, covers two independent tiers, and lists only live capabilities. It does not address read-only behavior, output shape, or potential errors, but it does provide meaningful behavioral context beyond the tool name.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded with what the tool returns, followed by important caveats. Each sentence contributes useful information, though the caveats could be tightened slightly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter informational tool with no output schema, this description gives sufficient context: what the tool covers, what it deliberately excludes, and how tiers are scoped. It does not explain the exact return structure, but the high-level behavior is clear enough for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the schema provides nothing to clarify. The description appropriately explains what content the tool returns and what it intentionally omits, which is the main semantic information an agent needs.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns capability tiers for Defici and what each tier unlocks, distinguishing it from price-related or platform-overview tools. It lacks an explicit verb like 'returns' or 'gets', but 'available' and the detailed scope make the purpose clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this tool should be used when an agent needs to know current capability tiers, plan limits, or partner-tier features. It does not explicitly state when not to use it or mention alternatives among the siblings, so usage guidance is inferred rather than explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a clearly distinct resource or operation: listing search, listing detail, regions, categories, modules, platform overview, and subscription info. The descriptions also explicitly prevent confusion, such as noting that get_platform_overview is not a listings search result.
Tool names follow a readable snake_case verb-first pattern: get_ for detail/info tools, list_ for enumerations, and search_ for queries. The main inconsistency is get_regions returning a full list while list_categories and list_modules use the list_ prefix for the same kind of enumeration.
Seven tools is well-scoped for a read-only marketplace discovery server. Each tool provides a necessary capability without redundancy, and the count stays comfortably in the ideal range.
For its stated read-only discovery purpose, the surface is complete: search active listings, fetch listing details, retrieve region and category taxonomies, and understand platform context, modules, and subscription capabilities. No obvious dead ends or missing core operations exist within the declared scope.
