Skip to main content
Glama
Sign In
controld-mcp

controld-mcp

by SwaggyMike
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List custom rules

list_profile_rules
Read-onlyIdempotent

Retrieve all custom rules for a specific profile to review or audit DNS filtering configurations. Provide a profile name or ID to return its complete rule list.

Instructions

List all custom rules for one profile.

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": {
      "profile": "<profile>"
    },
    "name": "list_profile_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYesExact profile name or profile ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered. The description adds the scope constraint ('for one profile') but doesn't describe any additional behavior like pagination, return format, or error handling. Since annotations carry the safety burden, a 3 is appropriate.

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 one concise sentence, front-loaded with action and resource. Every word adds value; no fluff.

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

Completeness5/5

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

For a simple list operation with one required parameter and no output schema, the description fully covers what the tool does. It names the resource, scope, and implies the parameter. Complete for 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 coverage is 100% – the schema describes 'profile' as 'Exact profile name or profile ID'. The description adds 'for one profile' which reinforces that it's a single profile. No extra semantic value beyond schema, but baseline is 3 when schema is fully descriptive.

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 'List all custom rules for one profile' clearly states the action (list), the resource (custom rules), and the scope (for one profile). It distinguishes from siblings like list_profiles (which lists profiles) and create_*_rules (which creates rules). No ambiguity.

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

Usage Guidelines4/5

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

The description implies when to use: to fetch custom rules for a specific profile. Given the sibling names (create_*_rules, delete_rules), the context is clear. It doesn't explicitly state when not to use, but the read-only nature is obvious. Could mention that profile must be exact from list_profiles, but that's implicit in schema.

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