Skip to main content
Glama

Wildberries API: информация о токене

wb_token_info
Read-only

Decode a Wildberries API token locally to inspect token type, expiry, access categories, read-only status, and seller ID, helping diagnose why API calls return 403 errors.

Instructions

Локально декодирует WB API токен (без запросов в WB): тип токена, срок действия, категории доступа, признак «только чтение» и ID продавца. Помогает понять, почему метод возвращает 403.

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": "wb_token_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: decoding happens locally with no WB requests, so no network dependency or credentials are needed at call time. It also enumerates the decoded facets, though these overlap with the existing output schema.

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?

Two sentences, no filler, with the core action and the local-only constraint front-loaded and the diagnostic use case second. Every clause carries information.

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?

For a zero-parameter, read-only utility with annotations and an output schema, the description supplies everything an agent needs to decide to call it and what it will learn. Return-value details are correctly left to the output schema.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The description is consistent with the empty schema rather than implying any input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource — "Локально декодирует WB API токен" — and immediately distinguishes it behaviorally from network-calling siblings with "без запросов в WB". It does not explicitly differentiate itself from the token-related sibling wb_refresh, so an agent must infer that distinction.

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?

It gives a concrete trigger for use: diagnosing why a method returns 403. That is real when-to-use guidance, but there are no exclusions or named alternatives (e.g., that refreshing a token belongs to wb_refresh rather than here).

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