Skip to main content
Glama
Sign In

Florida Code

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Fl Statute

fl_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the Florida Statutes — Florida state law — by citation. "Florida Statute 784.011" is section 784.011 (assault). Returns the statutory text, its catchline and its amendment history. Keyless. Use for "what does Florida Statute 316.193 say", "text of Fla. Stat. 768.28", or to check a Florida 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": "784.011"
    },
    "name": "fl_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesSection as cited, e.g. "784.011" or "316.193". The chapter is the part before the dot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly, openWorld, idempotent, and non-destructive behavior. The description adds value by disclosing the return contents (statutory text, catchline, amendment history) and noting keyless access, which goes beyond what annotations state. No contradiction found.

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?

The description is compact and front-loaded: the first sentence states the core purpose, followed by a concrete example, return contents, and usage prompts. Every sentence earns its place with no redundancy or fluff.

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 no output schema, the description explicitly states what the tool returns (statutory text, catchline, amendment history) and includes representative input examples. For a simple one-parameter lookup tool, this is complete—an agent knows what to provide and what to expect.

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?

The schema covers the single parameter 'section' at 100% with a clear description of format and examples. The tool description doesn't add significant meaning beyond what the schema provides—it only reiterates the citation format. Per guidelines, baseline 3 is appropriate when schema does the heavy lifting.

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?

The description clearly identifies the verb (Get), the resource (Florida Statutes section), and the scope (FULL TEXT by citation). It distinguishes itself from sibling tools which are mostly market/research related, and provides specific examples that clarify exactly what it does.

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?

The description gives explicit usage examples ('Use for "what does Florida Statute 316.193 say"') and notes it's keyless, which sets clear expectations. It does not mention alternatives, but among the listed siblings there is no obvious alternative for statute lookup, so the guidance is sufficient for an agent to select it appropriately.

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

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