Skip to main content
Glama
Sign In
waiaas

waiaas

by waiaas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_provider_status

Retrieve the provider status for a smart account: provider name, supported chains, and gas sponsorship (paymaster) status by providing a wallet ID.

Instructions

Get Smart Account provider status: provider name, supported chains, gas sponsorship (paymaster) status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "wallet_id": "<wallet_id>"
    },
    "name": "get_provider_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
wallet_idYesTarget wallet ID (UUID).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.11.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It implies a read operation ('Get...') but does not explicitly state read-only behavior, auth requirements, or other side effects. It adequately discloses the output type but lacks some behavioral detail.

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?

A single sentence that conveys the tool's purpose and key outputs without any extraneous words. Highly efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description lists three key outputs (provider name, supported chains, gas sponsorship status), which is sufficient for a simple status retrieval. It could mention that the response is for the given wallet, but that is implied by the input parameter.

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% (wallet_id is fully described in schema). The tool description adds no extra meaning beyond the schema; it does not clarify the wallet_id's role in the context of provider status. Baseline 3 is appropriate.

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's purpose: 'Get Smart Account provider status' and lists specific outputs (provider name, supported chains, gas sponsorship status). This distinguishes it from siblings, none of which mention 'provider'.

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 implicitly indicates when to use the tool (to retrieve provider status for a smart account). No explicit alternatives are given, but given its unique focus, no sibling overlaps, so usage context is clear.

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

Deploy Server

Other Tools