Skip to main content
Glama
kaminari-ad

@kaminari-ad/mcp

Official
by kaminari-ad

Get Custom Rule

get_custom_rule
Read-onlyIdempotent

Retrieve a specific custom rule by UUID to access its name, tag-slug, type, configuration, target, and active status.

Instructions

Get one custom rule by UUID with name, tag-slug, type, config object, target, active flag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rule_idYesRule UUID.

Implementation Reference

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds value by specifying the exact fields returned (name, tag-slug, type, config object, target, active flag), providing behavioral context beyond the safe-read nature implied by annotations.

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 sentence of 16 words, front-loading the action and key fields. It contains no fluff or redundant information, earning its place efficiently.

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 low-complexity tool (1 parameter, no output schema, no enums), the description adequately conveys the return structure by listing fields. It is complete enough to understand the tool's purpose and behavior, though a mention of error cases or response format could enhance it.

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 for the single parameter 'rule_id' is 100% with a description 'Rule UUID.'. The description does not add any additional meaning beyond the schema, meeting the baseline for high coverage. No extra semantics are provided.

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 uses the specific verb 'Get' and identifies the resource as 'one custom rule by UUID'. It lists the fields returned (name, tag-slug, type, config object, target, active flag), clearly distinguishing from sibling tools like list_custom_rules.

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 by stating 'Get one custom rule by UUID', but it lacks explicit guidance on when to use this tool versus alternatives like list_custom_rules, or any prerequisites. The usage context is clear enough but not elaborated.

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/kaminari-ad/mcp'

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