Skip to main content
Glama
Sign In

Mississippi Code

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ms Code Search

ms_code_search
Read-onlyIdempotent

Search the Mississippi Code of 1972 BY TOPIC or keyword rather than citation — "security deposit", "concealed carry", "DUI per se limit", "homicide". Matches against every section's official CATCHLINE across the whole Code (not full statutory body text — there is no full-text search anywhere in this source chain; the official LexisNexis tool, Justia, and FindLaw all sit behind the same Cloudflare bot-check, confirmed live). Returns matching citations, titles, and catchlines; call ms_code_section with a citation for the full text. 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": {
      "query": "security deposit"
    },
    "name": "ms_code_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return, default 10, max 25.
queryYesTopic or keywords, e.g. "security deposit return".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, but the description adds substantial context: keyless access, catchline-only matching, no full-text search in the source chain, Cloudflare bot-check constraints, and the exact return fields. This is rich behavioral disclosure beyond structured 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?

Front-loads the core action and query style, then adds the crucial catchline limitation, return shape, and next-tool routing. The parenthetical context is dense but earns its place by preventing full-text search attempts.

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?

No output schema exists, but the description fully explains what is returned: matching citations, titles, and catchlines. It also covers the key limitation, keyless access, and the logical next tool, leaving no material gap for correct invocation.

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 documents both parameters, so the baseline is 3. The description adds meaningful query semantics by specifying topic/keyword use rather than citation and gives concrete examples such as "security deposit" and "concealed carry"; it does not add detail about limit, which the schema already covers.

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: search the Mississippi Code by topic or keyword rather than citation. The description clearly distinguishes this tool from citation-based lookup and from full-text search, and names ms_code_section as the follow-up for full text.

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 says to use topic/keyword queries rather than citations and directs the agent to call ms_code_section with a citation for full statutory text. It also clarifies the catchline-only limitation, which tells the agent when not to expect full-text results.

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