Skip to main content
Glama

taxonomy_list_terms

Retrieve taxonomy terms from Paperlib MCP to organize academic literature by categories, enabling structured classification of research papers.

Instructions

列出词表规则

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNo
enabled_onlyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'taxonomy_list_terms' tool. It queries the 'taxonomy_terms' table from the database, optionally filtering by 'kind' and 'enabled_only' parameters, and returns the list of terms.
    @mcp.tool()
    def taxonomy_list_terms(
        kind: str | None = None,
        enabled_only: bool = True,
    ) -> dict[str, Any]:
        """列出词表规则"""
        try:
            where = []
            params = []
            if kind:
                where.append("kind = %s")
                params.append(kind)
            if enabled_only:
                where.append("enabled = TRUE")
            where_sql = " WHERE " + " AND ".join(where) if where else ""
            
            rows = query_all(f"""
                SELECT term_id, kind, family, pattern, priority, enabled, notes
                FROM taxonomy_terms
                {where_sql}
                ORDER BY kind, priority ASC, family
            """, tuple(params))
            return {"terms": rows}
        except Exception as e:
            return {"error": str(e)}
  • Registration of the graph_v12 tools suite, which includes the 'taxonomy_list_terms' tool, by calling the register_graph_v12_tools function on the MCP instance.
    register_graph_v12_tools(mcp)
  • Import of the register_graph_v12_tools function used to register the tools including 'taxonomy_list_terms'.
    from paperlib_mcp.tools.graph_v12 import register_graph_v12_tools
Behavior1/5

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

No annotations are provided, so the description carries full burden. It only states the action ('list') without disclosing behavioral traits like pagination, sorting, permissions needed, rate limits, or what 'rules' entail. This is inadequate for a tool with parameters and 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?

The description is a single phrase, front-loaded with no wasted words. It is appropriately sized for its limited content, though this conciseness comes at the expense of detail.

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

Completeness2/5

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

Given 2 parameters with 0% schema coverage, no annotations, and an output schema (which reduces need to describe returns), the description is incomplete. It lacks essential details on purpose, usage, parameters, and behavior, making it insufficient for effective tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no information about parameters. Parameters 'kind' and 'enabled_only' are undocumented in both schema and description, failing to compensate for the coverage gap.

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

Purpose2/5

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

The description '列出词表规则' (List vocabulary rules) restates the tool name 'taxonomy_list_terms' in Chinese, making it tautological. It lacks specificity about what 'terms' or 'rules' refer to (e.g., taxonomy terms, classification rules) and does not differentiate from sibling tools like 'taxonomy_upsert_term'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. It does not mention sibling tools (e.g., 'taxonomy_upsert_term' for creating/updating terms) or contextual prerequisites, leaving usage unclear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/h-lu/paperlib-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server