Skip to main content
Glama

List block rules

list_rules
Read-only

Lists block rules showing which tables and columns are never sent to the AI; omit source to view rules across all sources.

Instructions

List the user's block rules: the tables and columns never sent to the AI. Leave source out for every source.

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_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real semantic context by explaining that returned rules are the tables/columns withheld from the AI, but says nothing about ordering, size, or what an empty result means.

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?

Two sentences, no filler, with the resource definition front-loaded ahead of the parameter hint. The phrasing "Leave `source` out for every source" is slightly terse and could read ambiguously at a glance, but nothing is wasted.

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 read-only list tool with one optional parameter and no output schema, the description covers what is returned conceptually and how to get the unfiltered listing. Only the accepted form of `source` values is missing, which is a modest gap at this complexity level.

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 0%, so the schema alone gives only `source` with a null default and no explanation. The description partially compensates by stating that omitting `source` lists rules across every source, but it never says what values `source` accepts (presumably identifiers from `list_sources`) or what happens with an unknown value.

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 the user's block rules") and immediately defines what a block rule is: "the tables and columns never sent to the AI." That definition distinguishes it from generic listing tools, though it never names the sibling `block` tool as the mutating counterpart.

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?

Usage is implied by the resource name and the note "Leave `source` out for every source" gives a concrete calling pattern for the default case. There is no explicit when-to-use versus the `block` tool, nor any statement about prerequisites or when a source-scoped listing is preferable.

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