Skip to main content
Glama
Sign In

birdfury

by io.github.Joonsense
OverviewDiscussionsAdmin

Get result bundle

get_result_bundle
Read-onlyIdempotent

Read the canonical result bundle projection for a private request.

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": {
      "request": "<request>"
    },
    "name": "get_result_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesNumeric request id returned by create_paid_request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +{}
  2. Changed4 schema fields changed
    • addedInput schema / properties / request / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,15}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / request / exclusiveMinimum
      Removed value: -0
    • removedInput schema / properties / request / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / request / type
      Removed value: -"integer"
  3. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds only the 'private' scoping hint, and says nothing about authorization requirements, what happens if the bundle isn't ready, or errors.

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?

One sentence with no wasted clauses and the resource is front-loaded. Density of undefined jargon ('canonical', 'projection') slightly reduces immediate comprehension.

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?

For a one-parameter read tool with full annotations, the definition is minimally sufficient. It omits what the bundle actually contains and when it becomes available, which matters given the sibling tool set revolves around request/submission lifecycle.

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 single parameter is documented as the numeric request id from create_paid_request. The description contributes no additional meaning about the identifier or accepted formats, so baseline 3 applies.

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?

States a specific verb ('Read') and resource ('canonical result bundle projection') scoped to a private request. It is distinguishable from status-oriented siblings like get_request_status, but the term 'result bundle projection' is unexplained jargon that an agent must infer.

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

Usage Guidelines2/5

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

No guidance on when to call this versus get_request_status, get_submission_status, or get_mission, all of which appear related. No preconditions (e.g., request must be completed or reviewed) are stated, so the agent must guess timing.

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