Verify Vibo API connectivity and authentication by fetching the current user; returns ok:true with account ID to confirm working credentials.
Verify connectivity and authentication to the Vibo API by fetching the current user. Returns ok:true with your account id when credentials work.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.5.1v1.4.3v1.3.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description adds context beyond annotations by specifying the return values (ok:true and account id) and authentication requirement, with no contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no wasted words, purpose stated upfront.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter read-only tool, description covers purpose, authentication, and return format completely, given annotations provide safety assurance.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist; description adds full meaning by describing tool behavior, meeting the baseline for zero-param tools.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the tool verifies connectivity and authentication by fetching the current user, distinguishing it from sibling tools that perform specific operations like listing or modifying events.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implied usage is for health checks before other operations, but lacks explicit when-to-use vs alternatives or when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.