Skip to main content
Glama

Catch records

get_catch_reports
Read-onlyIdempotent

Get catch records by date or freshness tier. Returns the catch date, the region (district name), the blog post URL when published (records whose blog post is not published yet are included, without a blog URL) and, for records registered on the Midnight blockchain, a verify link per batch. Exact GPS coordinates are never returned: on v3 records the exact position is not on the chain (only a commitment to it); the district name is a label set by GYOTAK. GYOTAK checks the region range when recording, but the range used is not part of the record, so a third party cannot confirm it from the chain; GYOTAK can disclose the position of a record individually. In-stock products reference these records by date. To check a record on-chain without trusting GYOTAK, open its verify link, or call verify_catch with network "mainnet", the v3 contract address given in the response and the batch ID.

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_catch_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD format. Returns records for that specific date.
tierNoFreshness tier: fresh=last 30 days, tier1=31-60 days, tier2=61-90 days

Output Schema

NameRequiredDescriptionDefault
countYes
limitNoPresent when only the most recent records are shown
reportsYes
verifyCatchContractNoArguments for verify_catch on v3 records

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "type": "integer"
      +    },
      +    "limit": {
      +      "description": "Present when only the most recent records are shown",
      +      "type": "integer"
      +    },
      +    "reports": {
      +      "items": {
      +        "properties": {
      +          "blogUrl": {
      +            "type": "string"
      +          },
      +          "createdAt": {
      +            "type": "string"
      +          },
      +          "date": {
      +            "type": "string"
      +          },
      +          "location": {
      +            "description": "District name (or \"Unknown\")",
      +            "type": "string"
      +          },
      +          "onchain": {
      +            "items": {
      +              "properties": {
      +                "batchId": {
      +                  "type": "string"
      +                },
      +                "scheme": {
      +                  "enum": [
      +                    "v3",
      +                    "legacy",
      +                    "out_of_scope"
      +                  ],
      +                  "type": "string"
      +                },
      +                "verifyUrl": {
      +                  "type": "string"
      +                }
      +              },
      +              "required": [
      +                "batchId",
      +                "scheme"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          }
      +        },
      +        "required": [
      +          "date",
      +          "createdAt",
      +          "location",
      +          "onchain"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "verifyCatchContract": {
      +      "description": "Arguments for verify_catch on v3 records",
      +      "properties": {
      +        "contractAddress": {
      +          "type": "string"
      +        },
      +        "network": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "network",
      +        "contractAddress"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "count",
      +    "reports"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial context the annotations cannot convey: unpublished records are still returned (without a blog URL), exact GPS is never returned and why (v3 stores only a commitment), the district name is a GYOTAK-set label the range is not recorded on-chain, and per-batch verify links are present for Midnight-registered records. That is rich provenance and limitation disclosure well beyond readOnlyHint/idempotentHint.

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 purpose and return contents, and most sentences carry real information about data provenance and verification. A few clauses (e.g. GYOTAK can disclose a position individually) are tangential to invoking the tool and could be trimmed.

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?

Even though an output schema exists, the description covers what an agent needs to interpret results correctly: missing blog URLs on unpublished records, absence of exact coordinates, the trust caveat around district labels, and the path to independent verification. Nothing material is left ambiguous for this read-only lookup 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% and the tier enum already spells out the day ranges, so the schema does the heavy lifting. The description reinforces that records can be fetched 'by date or freshness tier' and explains why dates matter (in-stock products reference records by date), but adds no format or edge-case detail beyond the schema.

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?

Opens with a specific verb and resource ('Get catch records') and names the two filtering axes (date, freshness tier). It also implicitly separates itself from siblings by pointing at verify_catch for on-chain verification and by describing the record shape, so an agent can tell it apart from get_komon_records or search_fish.

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?

Explicitly names the alternative verify_catch, including the exact arguments (network 'mainnet', v3 contract address from the response, batch ID) for verifying without trusting GYOTAK. It also notes that in-stock products reference these records by date, which tells the agent when a date lookup is meaningful. It stops short of stating when to prefer get_komon_records or search_fish instead.

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