Skip to main content
Glama

speechwire_select_user_account

Selects a SpeechWire user account by account ID to enable subsequent operations.

Instructions

Select a SpeechWire account to work with.

Parameters

account_id : int Account ID from speechwire_list_user_accounts.

Returns

dict Status record containing status (str) and account_id (int).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
Behavior4/5

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

No annotations provided, so description carries full burden. It describes the return as a status record with status and account_id, which is sufficient for a selection tool. Could mention that it sets the active account, but overall adequate.

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?

The description is concise and well-structured with clear Parameters and Returns sections. Every sentence adds value; no fluff.

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?

Given the tool's simplicity (one parameter, no output schema), the description provides complete context: what it does, where the parameter comes from, and what it returns. It is sufficient for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has no parameter descriptions (0% coverage). The description adds the meaning: 'Account ID from speechwire_list_user_accounts', which is essential for correct use.

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?

The description clearly states the tool selects a SpeechWire account, using a specific verb and resource. It distinguishes from siblings like speechwire_list_user_accounts by indicating it is for selection after listing.

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?

The description implies use after listing accounts and mentions the parameter comes from speechwire_list_user_accounts. It does not explicitly state when not to use or alternatives, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jessica-writes-code/speechwire-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server