Skip to main content
Glama
Sign In

Gillby

by io.github.OneWave-AI
OverviewDiscussionsAdmin

California protected-area source boundaries

get_california_protected_areas
Read-onlyIdempotent

Paginated CDFW protected-area boundary geometry from a dated archive. Verify current CDFW fishing and access regulations; geometry alone does not establish permitted activities.

Units: ft, kt, s, F, mi; directions FROM. Returns data and source/freshness metadata.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_california_protected_areas"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower. The description adds genuinely new behavioral context: results are paginated, drawn from a dated archive, and returned alongside source/freshness metadata. It stops short of noting rate limits or archive staleness caveats.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Two short paragraphs are front-loaded and readable, but the trailing unit line ('Units: ft, kt, s, F, mi; directions FROM') is cryptic and its applicability to geometry output is unclear, which mildly hurts scanning clarity.

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 does sensibly summarize the return shape (data plus source/freshness metadata), but the under-documented paging parameters and the unexplained unit convention leave gaps for an agent trying to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single nested query object (limit/offset with defaults and 10/1000 caps). The description says 'paginated' but never mentions limit, offset, their defaults, or max paging depth, so it fails to compensate for the coverage gap.

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 specific verb and resource ('Paginated CDFW protected-area boundary geometry from a dated archive') plus the authoritative source (CDFW, dated archive), which an agent can distinguish from generic geo tools. It does not, however, contrast itself with the sibling get_protected_areas, so differentiation is only partial.

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

Usage Guidelines3/5

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

It states a scope boundary ('geometry alone does not establish permitted activities; verify current CDFW fishing and access regulations') which implies this tool answers boundary questions only. But it never names an alternative tool or says explicitly when to prefer this over get_protected_areas or the other california_* tools.

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

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