Skip to main content
Glama
Sign In
YAPI MCP Server

YAPI MCP Server

by AlwaysLoveme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Interfaces by Category

yapi_list_by_category

Retrieve and paginate through API interfaces under a specific category by providing the category ID. Supports configurable page number and items per page.

Instructions

List interfaces belonging to a specific category with pagination.

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": {
      "cat_id": "<cat_id>"
    },
    "name": "yapi_list_by_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
cat_idYesThe category ID (obtained from yapi_get_cat_menu)
pageNoPage number (default: 1)
limitNoItems per page, max 100 (default: 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It mentions pagination, which is a useful behavioral clue, but does not disclose whether the operation is read-only, requires authentication, or has any rate limits or side effects.

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?

The description is a single, efficient sentence that conveys the essential purpose without extraneous words. It is appropriately front-loaded and concise.

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 no output schema, the description should ideally explain the return format, which it does not. It adequately describes the input and basic behavior (pagination) but lacks context on the response structure or edge cases.

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?

The input schema has 100% description coverage, so baseline is 3. The description only adds 'with pagination', which loosely relates to page and limit parameters but provides no additional semantics beyond what the schema already specifies.

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 clearly states the verb 'List' and resource 'interfaces belonging to a specific category with pagination', making the core function clear. However, it does not differentiate from the sibling tool 'yapi_list_interfaces', which likely lists all interfaces without category filter.

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 implies usage for listing interfaces in a specific category, but it does not explicitly state when to use this tool versus alternatives like 'yapi_list_interfaces' or 'yapi_get_interface'. No guidance on when not to use it is provided.

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