Skip to main content
Glama
Sign In
nemesis-shield

nemesis-shield

by eobi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

nemesis_omniguard_catalog

Read-only

List Omniguard sectors and events with their protections to select the right business-logic firewall. Describe what you're building to receive a suggested sector and event.

Instructions

List Omniguard sectors and events (and what each protects) so you can pick the right business-logic firewall for what the developer is building. Optionally pass a description to get a suggested sector+event.

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

Input Schema

NameRequiredDescriptionDefault
describeNoWhat they're building, e.g. 'an ecommerce checkout' or 'a fintech transfer API'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.4

TDQS

A4.5/5.0
Behavior4/5

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

The readOnlyHint annotation already signals it's read-only; the description adds the behavioral detail that passing a description returns a suggested sector+event. It doesn't describe output format or limitations, but for a simple catalog this adds sufficient transparency.

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 two sentences, front-loaded with the main action, and every word earns its place. No redundancy or filler.

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 one-optional-parameter, read-only tool with no output schema, the description fully covers what it does, when to use it, and what the parameter does. An agent has enough to invoke it correctly.

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

Parameters4/5

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

Schema coverage is 100% and the schema describes the parameter well ('What they're building'), but the description adds the effect of the parameter (get a suggested sector+event), which is meaningful beyond the schema and helps the agent understand how to use it.

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 specific verbs ('List') and resources ('Omniguard sectors and events'), explains the purpose (pick the right business-logic firewall), and differentiates from siblings by emphasizing it's a read-only catalog plus optional suggestion. It clearly states what the tool does.

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 provides clear context for when to use the tool ('for what the developer is building') and explains how the optional 'describe' parameter feeds into a suggestion. It doesn't explicitly mention when not to use it or name alternatives, so it falls just short of a full 5.

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