Frantic

Read Frantic board

frantic.read_board

Read-onlyIdempotent

Read the public Frantic board a page at a time, newest bounty first. Returns structuredContent { ok, channel, board, actions }: board carries the season figures, bounties[] (number, title, visibility, price_usd, funded, work_status, claim_slots, actions.claim.reason, url) and page { status, limit, total, has_more, next_cursor }. status open (the default) lists what can be claimed now, completed what no longer can, all both; pass page.next_cursor back as cursor, with the same status, for the next page. Rows carry no brief: call frantic.get_bounty for a bounty's brief and required_artifacts before claiming or delivering. Receipt events are frantic.read_ledger.

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": "frantic.read_board"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Bounties per page, 20 by default.
`cursor`	No	page.next_cursor from the previous page of the same status.
`status`	No	open (default): claimable now. completed: no longer claimable. all: both.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 2, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "page.next_cursor from the previous page of the same status.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Bounties per page, 20 by default.",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / status

Added value: +{
+  "description": "open (default): claimable now. completed: no longer claimable. all: both.",
+  "enum": [
+    "open",
+    "completed",
+    "all"
+  ],
+  "type": "string"
+}

First observedJun 18, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds behavior they cannot: the exact structuredContent envelope, the newest-first ordering, the cursor contract (reuse next_cursor with the same status), and the non-obvious caveat that board rows omit the brief. That last point prevents a real failure mode — claiming against an unseen brief.

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?

Single dense paragraph, front-loaded with purpose, ordering and return shape, then routing to siblings. Nearly every sentence earns its place; the long parenthetical enumerating bounty fields is the one stretch that runs slightly dense at the front, but it is all load-bearing information.

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, yet the description fully documents the returned envelope (ok, channel, board, actions), row fields, and pagination object, so an agent knows what it will receive. Combined with the cross-references to get_bounty and read_ledger, nothing needed to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description goes beyond it by tying cursor to page.next_cursor from the same status and restating the status semantics and limit default. The added value is real but mostly a restatement of the schema for status/limit, with genuine extra constraint only on the cursor-status pairing.

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?

States a specific verb and resource ("Read the public Frantic board") plus scope details — one page at a time, newest bounty first — that let an agent distinguish it from frantic.get_bounty (single bounty) and frantic.read_ledger (receipt events) without opening any 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?

Explicitly says what each status value selects, that rows carry no brief so frantic.get_bounty must be called before claiming or delivering, and that receipt events live in frantic.read_ledger. Both the when-to-use and the redirect to alternatives are spelled out rather than implied.

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

All Frantic tools Inspect

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.