Skip to main content
Glama

get_recent_stockings

Read-onlyIdempotent

Recent stocking events in one open state. Optional county and species. since_days defaults to 14 and must be from 1 to 90. Estimated dates keep the around wording and are not exact days. At most 25 events.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>"
    },
    "name": "get_recent_stockings"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesUS state abbreviation
countyNo
speciesNo
since_daysNoDays back from today, 1 to 90. Default 14.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare read-only, non-destructive, idempotent, closed-world behavior, so the safety bar is covered. The description adds genuinely useful behavior beyond that: a 25-event result cap and a data-quality caveat that estimated dates use "around" wording and are not exact days. It omits other behavioral context, such as ordering, whether results are paged, and how the state's "open" status is determined, so this lands at a solid 3 rather than higher.

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?

Five short, front-loaded statements with no filler; the result cap and date caveat are stated plainly. The style is telegraphic, and the since_days default/range sentence largely restates the schema, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 carries the burden of explaining the return, and it only partially does so: it discloses the 25-event ceiling and the estimated-date wording but not the shape or ordering of returned events. For a four-parameter read tool, this is adequate but leaves real gaps.

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 50%: state and since_days are already documented in the schema, including the 1-90 range and default, which the description partly repeats. The description does flag county and species as optional, but it gives no format guidance for either, such as which county or species names are accepted, so the uncovered parameters remain ambiguous. This is baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete resource and scope: "Recent stocking events in one open state," with optional county/species narrowing. It is a noun phrase rather than a verb+resource, and it never contrasts itself with siblings like get_water or search_waters, but an agent can still tell what it returns.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance and no named alternative, even though search_waters and get_water exist in the sibling set. The only guidance is implicit in the words "recent" and "one open state," which the agent must interpret on its own.

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.

Resources