Wiro MCP Server

Official

by wiroai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

List Wiro agent templates

list_agent_templates

Read-onlyIdempotent

Browse ready-made Wiro agent templates with Starter and Pro pricing and monthly credit pools, so you can find a priced agent to deploy. Skip templates with null pricing; fetch full details next.

Instructions

Browse the catalog of ready-made Wiro agents (templates) that deploy_agent can deploy. Each template shows its Starter and Pro price in USD per 30 days and the monthly credit pool that pays for the agent's chat and scheduled tasks (100 credits = 1 USD); model runs it starts, for images, videos or voice calls, are billed to the wallet of the Wiro API key saved on the agent. A template whose pricing is null cannot be priced right now: do not quote or deploy it. Call get_agent_template next for the skills, the credentials the user must provide and the exact prices. To build an agent from individual skills instead, use list_agent_skills. get_playbook describes the whole flow from choosing a template to a running agent.

Input Schema

Name	Required	Description	Default
`sort`	No	Order when no search is given: newest first, most deployed first, or by title.	newest
`limit`	No	Maximum templates to return (default 20, max 100).
`start`	No	Pagination offset (default 0).
`search`	No	Words to look for in the title, description, slug and categories, for example "instagram". Results are sorted by relevance when set.
`category`	No	Category filter, for example "social-media". Separate several categories with commas.

Output Schema

Name	Required	Description	Default
`limit`	Yes
`start`	Yes
`total`	Yes
`nextStart`	Yes
`templates`	Yes
`nextAction`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.4.1Nov 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare a safe read (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: the pricing model (Starter/Pro per 30 days in USD), the credit-pool math (100 credits = 1 USD), and that model runs bill to the wallet of the API key saved on the agent. The null-pricing caveat is an operational constraint an agent could not infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause and every sentence carries information (pricing, credit pool, billing target, null rule, next steps). The billing sentence is long and could be split, but there is essentially no 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 read-only catalog listing with an output schema and complete parameter documentation, the description covers what the agent needs: what is returned conceptually, how to interpret prices and credits, what null pricing means, and where to go next. Nothing material 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?

Schema description coverage is 100%, so sort, limit, start, search and category are fully documented in the schema itself. The description adds no additional meaning about these parameters, which is the baseline expectation when the schema does the work.

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?

States a specific verb and resource — browse the catalog of ready-made Wiro agent templates — and ties it directly to the deploy_agent consumer. It is clearly distinguished from get_agent_template (detail view) and list_agent_skills (building from individual skills).

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 routing: call get_agent_template next for skills/credentials/prices, use list_agent_skills to build from individual skills, and get_playbook for the end-to-end flow. It also gives a concrete exclusion rule — templates with null pricing must not be quoted or deployed.

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