Skip to main content
Glama
Sign In
SSW Rules MCP

SSW Rules MCP

by SSWConsulting
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Rule

get_rule

Retrieve the full content of a specific SSW Rule by its URI slug, including title, URL, metadata, and cleaned markdown with JSX removed.

Instructions

Get the full content of a specific SSW Rule by its URI slug.

Returns the rule's title, URL, metadata, and full cleaned markdown content. The content has JSX components stripped for clean reading.

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": {
      "uri": "<uri>"
    },
    "name": "get_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriYesThe rule URI slug (e.g. '3-steps-to-a-pbi', 'definition-of-done').

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a non-obvious behavioral trait: the returned content is cleaned markdown with JSX components stripped, so an agent knows not to expect raw source. It still omits error behavior for an unknown slug and any read-only/auth guarantees, though 'Get' strongly implies a safe read.

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?

Three short sentences, front-loaded with the action and key, with no filler. The middle sentence restates return fields that the output schema already defines, which is mild redundancy.

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?

An output schema exists, so return shape need not be re-explained, and the description covers purpose, key, and content processing adequately. It could be fully complete by pointing at search_rules as the way to obtain a slug.

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% and the schema already provides example slugs, so the description's 'by its URI slug' adds no syntax or meaning beyond it. Baseline 3 applies when the schema does the heavy lifting.

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 resource (a specific SSW Rule) plus the exact lookup key (URI slug), which separates it from the list/search siblings at a glance. It never names a sibling outright, so it falls short of a 5.

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 only an implicit hint that the caller must already know the slug ('by its URI slug'), which suggests search_rules might precede this call, but no when-to-use statement, no exclusions, and no alternatives are named.

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