Skip to main content
Glama
Sign In
seo-crawler-mcp

seo-crawler-mcp

by hna2810
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_taxonomy

Retrieve the complete Mother & Baby taxonomy with 12 main topics, subtopics, specific topics, content contexts, and locations to support content classification and SEO planning.

Instructions

Trả về toàn bộ bộ khung Taxonomy ngành Mẹ & Bé (12 Topic chính, danh sách Subtopic, Specific Topics, danh mục Content Context và danh sách Địa phương Location) để tham khảo.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, and the description does not mention any side effects, permissions, or whether the operation is read-only. The verb 'returns' suggests a read operation, but this is not explicitly stated, and there is no discussion of data persistence or external effects.

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?

The description is a single, concise sentence that directly states the tool's output and content. It avoids unnecessary detail and is well-structured for quick understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema and annotations, the description provides a moderate level of context by listing the taxonomy components. However, it does not specify the exact format or structure of the returned data, nor does it offer guidance on integration or typical use cases, which might be expected given the tool's reference nature.

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 has zero parameters, and the schema coverage is 100% (since there are no parameters to describe). According to the baseline for 0 parameters, a score of 4 is appropriate, as there is no parameter information to add.

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?

The description clearly states that the tool returns a taxonomy framework for the Mother & Baby industry, specifying the included components (12 main topics, subtopics, specific topics, content context, and local locations). This leaves no ambiguity about the tool's function.

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 mentions 'for reference' but does not explicitly state when to use this tool over sibling tools such as classify_content_topics or analyze_site_structure. While the purpose is clear, there is no direct guidance on when to choose this tool.

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

Deploy Server

Other Tools