Skip to main content
Glama
Sign In

Mississippi Code

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ms Code Chapters

ms_code_chapters
Read-onlyIdempotent

List the chapters within a title of the Mississippi Code of 1972, by title number ("97" is Crimes, "89" is Real and Personal Property, "27" is Taxation and Finance). Use this to browse a title when you do not have an exact section citation. Returns every chapter heading and number; call ms_code_section once you have a citation, or ms_code_search to find one by topic. Keyless.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": 97
    },
    "name": "ms_code_chapters"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesTitle number, e.g. 97 (Crimes) or 89 (Real and Personal Property). Mississippi titles are odd numbers 1-99.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description still adds two useful non-schema facts: the response shape ('Returns every chapter heading and number') and 'Keyless' (no authentication required). It does not mention pagination, result limits, or behavior on an invalid/out-of-range title number, which keeps it below a 5.

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?

Single front-loaded paragraph that leads with the action and scope, then usage guidance, then alternatives, then the auth note. Every clause carries distinct information; nothing is restated.

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 one-parameter, read-only listing tool with no output schema, the description covers purpose, selection criteria, return contents, and auth status — enough for correct invocation. Only edge cases (invalid title, empty result, truncation) are unaddressed, a minor gap given the tool's simplicity.

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% and the single parameter already carries a description with the same examples ('97 (Crimes)', '89 (Real and Personal Property)') plus the odd-number 1-99 constraint. The description's title examples largely duplicate the schema, so it adds little parameter meaning beyond what structured fields provide — baseline 3.

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?

States a specific verb and resource ('List the chapters within a title of the Mississippi Code of 1972') and adds concrete domain anchors ('97' is Crimes, '89' is Real and Personal Property). This is clearly distinguishable from ms_code_section (fetch a cited section) and ms_code_search (topic search) without opening any schema.

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

Usage Guidelines5/5

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

Explicitly names the situation that selects this tool ('Use this to browse a title when you do not have an exact section citation') and routes the agent onward to the two alternatives with their trigger conditions ('call ms_code_section once you have a citation, or ms_code_search to find one by topic'). Both when-to-use and when-to-use-something-else are present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mississippi Code toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources