Skip to main content
Glama
Sign In
SSW Rules MCP

SSW Rules MCP

by SSWConsulting
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Recent Rules

get_recent_rules

Retrieve recently updated SSW Rules within a specified lookback period, with an optional result limit, to track changes to best-practice guidance.

Instructions

Get recently updated SSW 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": "get_recent_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days to look back (default 30).
limitNoMaximum results (default 20).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It says nothing about sort order, whether results are newest-first, whether 'updated' versus 'created' matters, or any pagination behavior beyond the raw defaults. For a list tool with zero annotation coverage, this is a significant gap.

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 waste and the core concept front-loaded. It is efficient, though arguably under-specified rather than optimally concise for a tool with two behavioral parameters.

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

Completeness3/5

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

An output schema exists, so return values need not be explained. The parameters are fully documented in the schema, but the absence of annotations plus the lack of any usage routing or ordering semantics leaves real gaps for an agent deciding between this and its four siblings.

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 100%, with both days and limit fully documented in the schema, so the baseline of 3 applies. The description adds no syntax, unit, or interaction detail (e.g., whether limit truncates the most recent or oldest entries) beyond what the schema already provides.

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 (Get) and a well-defined resource (recently updated SSW Rules), which is clearer than a tautology. However, it does nothing to distinguish itself from the sibling search_rules or get_rule — an agent must infer that this is the chronological/browse variant rather than a search or single-fetch tool.

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 guidance on when to use this instead of search_rules, get_rule, or get_category_rules. 'Recently updated' hints at a recency-browsing use case, but no exclusions or alternative-routing conditions are stated.

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