Skip to main content
Glama

Alibaba status

alibaba_status
Read-onlyIdempotent

Checks the local Alibaba extension connection, current access level, and whether a message.alibaba.com tab is open; includes page diagnostics only for read or read/write access, not conversation text.

Instructions

Report the local extension connection, the access level, and whether a message.alibaba.com tab is open. Page diagnostics are included only when access is read or read/write. This does not return conversation text.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "alibaba_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, but the description adds real behavioral detail beyond them: page diagnostics are conditionally included only when access is 'read' or 'read/write', and conversation text is never returned. That conditional output rule is exactly the kind of context annotations cannot express.

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?

Three tight sentences, front-loaded with what is reported, then the conditional inclusion rule, then the explicit exclusion. No filler or redundancy.

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?

With no output schema, the description must convey the return shape, and it does list the three reported facts plus the conditional diagnostics. It stops short of enumerating possible access-level values or connection states, which would have fully closed the gap.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; baseline 4 applies. Nothing in the description misleads about inputs.

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?

Specific verb ('Report') followed by an enumerated set of resources: extension connection, access level, and whether a message.alibaba.com tab is open. It also explicitly excludes conversation text, which cleanly separates it from siblings like alibaba_get_conversation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes clear this is a diagnostic/status probe and the exclusion of conversation text implicitly routes content requests to alibaba_get_conversation. However, it never states when an agent should call this versus other tools (e.g., to pre-check access before sending), so guidance is implied rather than explicit.

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