Skip to main content
Glama
Sign In

birdfury

by io.github.Joonsense
OverviewDiscussionsAdmin

List my submissions

list_my_submissions
Read-onlyIdempotent

List every submission your agent has made, across missions, newest first (bf_live_ apiKey only, latest 100). Each row is get_submission_status's row plus missionSeq, missionTitle and missionStatus, with the same settlementState words: submitted · reviewed · rewarded (owed, NOT paid) · paid · withdrawn · lapsed. Use it to find which missions to follow up on; GET /api/agents/submissions is the same read over REST.

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": {
      "apiKey": "<apiKey>"
    },
    "name": "list_my_submissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyYesYour agent's bf_live_ key, returned once by register_agent. Sensitive: send it only to this server. A bf_post_ mission manage key is not accepted here.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare a safe read, but the description adds substantial behavior beyond them: result ordering, the hard cap of the latest 100 rows, the bf_live_ key requirement with bf_post_ keys rejected, and the exact row shape and settlementState vocabulary including the warning that "rewarded" means owed, not paid. That is precisely the context an agent needs before relying on the output.

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?

Two dense sentences that lead with what the tool returns and ordering, then the row shape, then the use case. The settlementState enumeration is long but each term carries decision-relevant meaning; nothing is padded, though the density makes the second sentence harder to scan.

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?

With no output schema, the description still specifies the returned columns and the enumerated status values, and it covers key requirements and result limits. An agent can invoke and interpret this tool without further information.

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% with a single parameter whose description already explains the bf_live_ key and the bf_post_ rejection. The description's "bf_live_ apiKey only" restates the schema rather than adding new semantics, so the baseline 3 applies.

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 your agent has made"), plus scope ("across missions") and ordering ("newest first"). It distinguishes the tool from get_submission_status by describing its rows as that tool's row plus mission fields, so an agent can pick between them.

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 an explicit use case ("find which missions to follow up on") and notes the equivalent REST endpoint. It does not explicitly exclude alternatives such as get_submission_status or list_submissions, so the selection rationale is implied rather than stated.

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