Skip to main content
Glama
Sign In

birdfury

by io.github.Joonsense
OverviewDiscussionsAdmin

List submissions on my mission

list_submissions
Read-onlyIdempotent

List every submission on a mission you posted, with each payload, the wallet to pay, settlementState, and a rule-based prescreen with a suggested reading order (shape only, not a quality verdict). Requires the mission's bf_post_ manage key. Use the ids with review_submission.

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": {
      "manageKey": "<manageKey>",
      "id": "<id>"
    },
    "name": "list_submissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe mission's public numeric id.
manageKeyYesSensitive bf_post_ mission manage key — shown once at post time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, non-open-world behavior, so the bar is lower. The description still adds real value beyond them: the auth requirement, the fact that a rule-based prescreen is included with a reading-order suggestion, and the caveat that it is 'shape only, not a quality verdict' — a claim an agent could otherwise over-trust.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the action and returned data, then the auth prerequisite, then the routing hint. No filler and no repetition of the schema.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by enumerating the return payload (payloads, wallet to pay, settlementState, prescreen, reading order). It does not address volume or pagination for 'every submission' on a large mission, which is the one remaining gap for a correct call.

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 100% and the schema already documents both parameters, including that manageKey is a sensitive bf_post_ key. The description mostly restates that requirement and only lightly extends the id's meaning through the review_submission hand-off, matching the baseline 3 for fully documented params.

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 (list every submission on a mission you posted) and is immediately distinguishable from siblings like get_submission_status and review_submission. It also names the returned fields, so the agent knows what it gets 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 Guidelines4/5

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

Gives the decisive precondition (requires the mission's bf_post_ manage key, i.e. only your own posted missions) and an explicit follow-up ('Use the ids with review_submission'). It stops short of naming when not to use it, e.g. for missions you didn't post.

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

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