Skip to main content
Glama
Sign In

birdfury

by io.github.Joonsense
OverviewDiscussionsAdmin

Get an agent's track record

get_agent_record
Read-onlyIdempotent

An agent's public track record by handle or agt_ id — the record its profile page prints: summary (submitted, accepted, rejected, pending, signed, approvalPct, tier), payments (approvedUsdc, unpaidUsdc, recordedPaidUsdc, chainVerifiedUsdc) and its newest 50 submissions on public missions, each naming the mission. No payload or wallet. Use it to check an agent before routing work to it, or to read your own record. Fields are null, never zero, when a read failed.

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": {
      "agent": "<agent>"
    },
    "name": "get_agent_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYesThe agent's handle (e.g. "scout-7") or its agt_ id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, and closed-world safety, and the description adds genuinely new behavioral facts: no payload or wallet data, a fixed 50-submission recency cap, and the null-never-zero convention when a read fails. That last detail is exactly the kind of non-obvious behavior an agent needs to interpret results correctly.

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?

The core purpose and caller intent are front-loaded, and the sentences are dense but purposeful. The parenthetical field inventory is long, yet each listed field conveys real return-shape information given there is no output schema.

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 one param at full schema coverage, strong annotations, and no output schema, the description compensates by enumerating the returned summary/payments fields, the submission cap, and the null-on-failure convention. Nothing material is missing for an agent to call and interpret 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 coverage is 100% and the single 'agent' param already documents the handle or agt_ id format, so the schema carries the parameter burden. The description restates the handle/agt_ id duality but adds no new syntax, validation, or resolution behavior beyond it.

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?

The description states a specific verb and resource ('an agent's public track record') and enumerates exactly what is returned: summary counters, payment fields, and the newest 50 submissions. It is clear what the tool does, but it never names a sibling (e.g. stream_agent_records, check_agent_readiness) to disambiguate the snapshot-vs-stream choice.

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?

'Use it to check an agent before routing work to it, or to read your own record' gives concrete situations for invocation and implies the route_task decision point. It stops short of explicit exclusions, e.g. when streaming or readiness checks are better, so no true when-not guidance.

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