Wiro MCP Server

Official

by wiroai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get a deployed Wiro agent

get_my_agent

Read-onlyIdempotent

Read a deployed agent's full state—status, plan, prices, credits, skills, channels, models, tasks, instructions, and credential status—and optionally wait while it starts or stops.

Instructions

Read the full state of one deployed agent: status (number and label), plan, its Starter and Pro prices, credit balance, time zone, skills, chat channels, model settings with the credit rates of the models it can switch to, scheduled tasks and custom instructions (a long text is shortened; entry adds one entry's whole text), and the state of each credential. Credential values are never returned, only whether each one is filled, connected or missing. With wait_seconds it keeps reading until the agent is no longer stopping, queued or starting; when the wait runs out, follow the returned nextAction instead of repeating the action that started it. Statuses: 0 stopped, 1 stopping, 2 queued, 3 starting, 4 running, 5 error, 6 setup required.

Input Schema

Name	Required	Description
`entry`	No	The key of one custom instruction or scheduled task, such as cs-brand-voice, or its bare name such as brand-voice. Adds that entry's whole text, which the list shortens when it is long. Read it before changing the entry with manage_agent_custom_skill.
`agent_guid`	Yes	The deployed agent's guid, from list_my_agents or deploy_agent.
`wait_seconds`	No	Keep reading for up to this many seconds while the agent is stopping, queued or starting (0 to 600, default 0 for an immediate read). 45 or less is safe for clients with a 60 second tool timeout; follow nextAction to keep waiting.

Output Schema

Name	Required	Description	Default
`agent`	Yes
`entry`	No
`advice`	Yes
`settled`	Yes
`nextAction`	No
`waitedSeconds`	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 readOnly/idempotent/non-destructive, yet the description still adds substantial behavioral detail: credential values are never returned (only filled/connected/missing), long instruction text is truncated unless entry is supplied, and the wait loop terminates with a nextAction directive. It also documents the full status code mapping, which is behavior an agent cannot infer elsewhere.

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?

The core action is front-loaded in the first clause, and the status legend is tucked at the end. The middle enumeration of returned fields is long but each item is meaningful for deciding whether this is the right call; no filler sentences.

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?

With an output schema present, return shape needn't be explained, yet the description still covers truncation behavior, credential redaction, polling semantics and status codes. Nothing an agent needs to invoke this correctly is missing.

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 100%, so the baseline is 3, but the description adds meaning the schema does not: entry unlocks the full untruncated text of one instruction/task, and wait_seconds is a polling window with guidance about the 60-second client timeout and nextAction. It goes beyond restating the schema.

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 ('Read the full state of one deployed agent') and then enumerates the exact facets returned (status, plan, prices, credit balance, skills, channels, model settings, tasks, credentials). This clearly distinguishes it from list_my_agents, which returns a list rather than one agent's full state.

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?

Gives concrete usage rules for the two optional parameters: use wait_seconds to poll while the agent is stopping/queued/starting, and follow the returned nextAction when the wait expires instead of repeating the initiating action. It also names manage_agent_custom_skill as the follow-up for editing an entry. It does not explicitly contrast with list_my_agents or update_agent, so no exclusion guidance.

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