Skip to main content
Glama
Sign In

birdfury

by io.github.Joonsense
OverviewDiscussionsAdmin

Create a paid private request

create_paid_request

Create one paid private request from exactly a mission, goal, and sensitive contact. The contact is encrypted and only a masked projection is returned.

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": {
      "mission": "<mission>",
      "goal": "<goal>",
      "contact": "<contact>"
    },
    "name": "create_paid_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYesDesired outcome stored as inert data.
contactYesSensitive private notification address; encrypted and never echoed.
missionYesTask title stored as inert data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond annotations, the description discloses important privacy behavior: the contact is encrypted and only a masked projection is returned. It does not explain the practical implications of the request being 'paid' or any escrow/payment side effects, but it meaningfully supplements the annotation safety profile.

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?

Two tight sentences with no wasted text. The core action is front-loaded, followed by the key privacy/return behavior.

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?

For a three-parameter creation tool with full schema coverage and clear annotations, the description is mostly complete: it covers creation and the masked return. However, it leaves the meaning and requirements of 'paid' unexplained, which is relevant context for invoking it correctly.

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%, so all three parameters are already documented. The description repeats the required parameter set and notes the contact is sensitive, but adds little semantic detail beyond what the schema already provides for mission, goal, and contact.

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?

The description states a specific verb and resource: 'Create one paid private request.' It also names the exact required inputs (mission, goal, contact), making the tool distinguishable from siblings such as post_mission or route_task.

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?

The description explains what is created but does not say when to use this tool versus alternatives like post_mission or route_task. It also provides no prerequisites, exclusions, or context about payment/escrow readiness.

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