Skip to main content
Glama

Nexscope Ecommerce Data MCP

ET TikTok Level 2 Categories

nexscope_data_et_category_l2
Read-only

List second-level categories, optionally under a top-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_l2"
  }
}

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 without the description. The description adds that the parent filter is optional, meaning an unfiltered call returns the full level-2 set, but says nothing about pagination, result limits, or ordering. With annotations carrying the safety burden, this is adequate but thin.

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: verb, resource, and the optional filter modifier in order of importance. Nothing is wasted, though the same word budget could have carried one more concrete fact.

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 simple read-only two-parameter listing tool with full schema coverage and no output schema, the definition is largely sufficient, and telling an agent it may omit parentId is the key operational fact. The remaining gap is not stating whether results are paginated or bounded, which matters for a list call that can be made unfiltered.

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%, so both parameters are already documented and the baseline is 3. The description does add real meaning by clarifying that parentId is a top-level (level-1) category ID rather than an arbitrary category, which sharpens the bare 'Parent category ID' in the schema. The language parameter gets no mention but is fully covered by its enum.

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?

States a specific verb and resource ('List second-level categories') and the level is explicit, which implicitly separates it from the l1/l3 sibling tools. It stops short of naming any sibling or stating scope boundaries, so an agent must infer the distinction from the level number alone.

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 top-level category' implies when the parentId filter applies, giving a workable usage cue. There is no explicit when-to-use guidance versus category_l1/category_l3/category_detail and no stated preconditions, so the correct selection is only implied.

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