Skip to main content
Glama

list_cnreport_rules

Read-onlyIdempotent

Browse and filter CN report extraction rules for LLM and script parsing by module, indicator, document type, or kind to locate reusable extraction logic.

Instructions

Browse cn-report's extraction rules (llm_rules + script_rules).

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

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
moduleNo
indicatorNo
document_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the useful fact that both llm_rules and script_rules are included, but says nothing about filtering behavior, the meaning of limit, or result volume. Modest added value on top of a strong annotation set.

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 short sentence with no filler, and the resource is front-loaded. It is efficient, though the terseness comes at the cost of needed detail rather than being a model of tight writing.

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?

An output schema and annotations exist, so return values and safety need not be explained, but five filter parameters with zero schema descriptions and no usage guidance leave real gaps. For a faceted browse tool, the definition does not tell an agent how to narrow results or what the filters mean.

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

Parameters2/5

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

Schema description coverage is 0% across five parameters (kind, limit, module, indicator, document_type), so the description carries the full burden. It only obliquely hints at rule kinds via 'llm_rules + script_rules' and never explains module, indicator, document_type, or the default limit of 100.

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 names a specific verb ('Browse') and resource ('cn-report's extraction rules') and clarifies the two rule families covered (llm_rules + script_rules). It is clear what the tool returns, but it does not distinguish itself from siblings such as list_concepts or list_bindings, which also sound like listing tools.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no stated alternatives or exclusions. 'Browse' only weakly implies exploratory listing, leaving the agent to guess whether this or a sibling listing tool is appropriate for a given query.

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