Wiro MCP Server

Official

by wiroai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

List Wiro agent skills

list_agent_skills

Read-onlyIdempotent

List available Wiro agent skills with monthly prices, dependencies, and required credentials to plan custom builds or skill changes and know what setup details to request.

Instructions

List the skills a Wiro agent can have, with their monthly price, the skills they depend on and the credential each one needs. Use it to plan a custom build for deploy_agent or a skill change for apply_agent_skills. Without name it lists every skill with its title and price: look there for the service the user named (apply_agent_skills also answers an unknown name with close matches). Pass name with a skill name (or a credential or channel key such as "telegram") to get the exact fields the user must provide, with their labels, formats and setup help, so you know what to ask for before calling set_agent_credentials or connect_agent_oauth.

Input Schema

Name	Required	Description
`name`	No	A skill name (for example "int-gmail-check") returns its price and the setup fields of every credential it needs. A credential or channel key (for example "telegram") returns that credential's setup and the ways it can connect.
`category`	No	"int" for skills that connect to an outside service, "util" for helper skills.
`capability`	No	Only skills with this capability, for example "image_generation". include_capabilities lists the names.
`include_deprecated`	No	Also return deprecated skills.
`include_capabilities`	No	Also return the list of capability names with descriptions.

Output Schema

Name	Required	Description	Default
`setup`	No
`total`	Yes
`skills`	Yes
`channels`	Yes
`nextAction`	No
`pricingNote`	Yes
`capabilities`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.4.1Nov 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so safety is covered; the description adds the meaningful behavioral fact that output shape changes entirely based on whether `name` is supplied, and that credential/channel keys are also resolvable. It does not mention pagination or result size for the unfiltered listing, which is the remaining gap.

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?

Three sentences, front-loaded with what is returned, then the usage routing, then the parameter-driven mode. Mostly waste-free, though the `name` semantics are stated twice (in the description prose and again in the schema), which is slight redundancy.

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?

An output schema exists so return shapes need not be spelled out, and the description still conveys the conceptual difference between the two return modes. Combined with the downstream-tool pointers, an agent has everything needed to call this correctly.

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 coverage is 100% and the schema already documents the dual meaning of `name`, the `category` enum, `capability`, and the two include_ flags. The description restates the `name` semantics (including the 'telegram' example) without adding format or edge-case detail beyond the schema, so baseline 3 applies.

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 (list agent skills) plus the payload contents: monthly price, dependencies, and required credentials. It is clearly distinguishable from siblings like deploy_agent, apply_agent_skills, and set_agent_credentials, which are named as downstream consumers rather than alternatives.

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?

Explicitly routes two modes: no `name` for discovery when planning a build or a skill change, `name` for retrieving exact setup fields before calling set_agent_credentials or connect_agent_oauth. It even names the fallback path (apply_agent_skills returns close matches for unknown names), so the agent knows the recovery route.

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