Skip to main content
Glama

Nexscope Ecommerce Data MCP

ET TikTok Level 3 Categories

nexscope_data_et_category_l3
Read-only

List third-level categories, optionally under a second-level category.

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": {
      "language": "<language>"
    },
    "name": "nexscope_data_et_category_l3"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageYesResponse language.
parentIdNoParent category ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the hierarchy-depth constraint and says nothing about result volume, ordering, or what an empty/unmatched parentId yields — useful but thin context beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler; nothing is wasted. Its brevity borders on under-specification rather than verbosity, but as structure it is clean and readable.

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?

For a two-parameter read-only listing tool with full schema coverage, no output schema, and existing annotations, the definition covers what is needed to invoke it correctly. It leaves minor questions open — whether omitting parentId returns every L3 category across all parents, and whether results are paginated — but nothing blocking.

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 coverage is 100%, so the enum values for language are fully documented in the schema. The description does add one piece of meaning the schema lacks: that parentId must reference a second-level category, narrowing what "Parent category ID" means. That is a modest gain over a complete schema, so baseline 3 holds.

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 gives a specific verb and resource ("List third-level categories") and its "third-level" qualifier distinguishes it by depth from the et_category_l1/l2 siblings. It stops short of naming those siblings explicitly, so the differentiation is inferable rather than stated.

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?

"Optionally under a second-level category" is the only usage signal; it tells the agent when to supply parentId but not when to use this tool versus category_l1, category_l2, or category_detail. No exclusions or prerequisites are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources