Skip to main content
Glama

Wy Search

wy_search
Read-onlyIdempotent

Search the Wyoming Statutes BY TOPIC or keyword rather than citation, "landlord security deposit", "concealed firearm permit", "murder penalty". Full-text search over the statutory body text across all titles (except Title 97, the Constitution). Returns matching citations and headings; call wy_statute 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": {
      "limit": 10,
      "query": "landlord"
    },
    "name": "wy_search"
  }
}

Input Schema

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

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, open-world, so the safety profile is covered. The description adds genuinely non-structured facts: full-text coverage across all titles except Title 97 (the Constitution), the shape of results (matching citations and headings), and that the tool is keyless. It does not discuss ranking or result ordering, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the search mode and the citation contrast before the coverage caveat and the handoff to wy_statute — a good information order. The quoted example queries partially duplicate the schema's example, which is the only wasted material in an otherwise tight paragraph.

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?

There is no output schema, so the description carries the return-shape burden and does: 'matching citations and headings'. Combined with the coverage exclusion (Title 97), the keyless note, and the pointer to wy_statute for full text, an agent has everything needed to call and to route results for a two-parameter read tool.

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%, so the schema already documents both query and limit (including default 10 and max 25). The description adds only the semantic framing that the query is a topic rather than a citation, reinforcing what the schema's own example shows. Baseline 3 is appropriate.

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?

Specific verb plus resource ('Search the Wyoming Statutes') with an explicit scope contrast: BY TOPIC or keyword 'rather than citation'. The quoted example queries concretize the input, and the scope is bounded (all titles except Title 97). An agent can distinguish this from a citation-lookup tool without opening the 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?

States the selecting condition positively (topic/keyword queries), negatively (not for citation lookup), and prescribes the follow-up action: 'call wy_statute with a citation for the full text'. This is explicit when-to-use plus explicit next step, leaving nothing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.