Skip to main content
Glama
Sign In

Michigan Code

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Mi Compiled Law

mi_compiled_law
Read-onlyIdempotent

Get the FULL TEXT of a section of the Michigan Compiled Laws — Michigan state statutes — by citation. "MCL 750.316" is first degree murder. Returns the statutory text only: the catchline and body of the section. The History line (acts that enacted or amended it) and editorial notes are not included in the stored copy; the text_scope field says what a given answer contains. Keyless. Use for "what does MCL 750.316 say" or to check a Michigan statute a case relies on.

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": {
      "section": "750.316"
    },
    "name": "mi_compiled_law"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesSection as cited, e.g. "750.316" or "257.625". Chapter is the part before the dot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, openWorld), and the description adds substantive context beyond them: it discloses exactly what is returned (catchline + body only), what is deliberately omitted (History line, editorial notes), that a text_scope field signals coverage, and that the tool is keyless. This is precisely the behavioral disclosure an agent needs that annotations cannot carry.

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?

Front-loads the core verb phrase 'Get the FULL TEXT' and proceeds through return scope, exclusions, and use cases with no wasted sentences. Slightly dense (em-dashes, multiple clauses) but every element earns its place.

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?

With one required parameter covered 100% and no output schema, the description must explain return values — and it does, detailing contents, exclusions, and the text_scope field. Nothing an agent needs to call or interpret the tool is missing.

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%, establishing a baseline of 3, but the description adds value by showing that the input is a citation string and that an 'MCL 750.316' form maps to the section parameter. This complements the schema's 'chapter is the part before the dot' note without fully duplicating 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?

States a specific verb and resource ('Get the FULL TEXT of a section of the Michigan Compiled Laws ... by citation') and immediately anchors it with a concrete citation example. No sibling tool in the list overlaps with statute retrieval, so the agent can select it unambiguously.

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?

Gives explicit trigger phrases ('what does MCL 750.316 say' or to check a Michigan statute a case relies on), which tells the agent clearly when to reach for it. No alternative tools or exclusions are named, but none of the siblings compete for this scope, so the guidance is adequate.

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

All Michigan 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