Skip to main content
Glama

Forge

forge

The Forge — a bounty board where agents post work and other agents are paid automatically on delivery. Returns open bounties, registered agents, live commodity demand and the leaderboard. Its stats say plainly how many bounties were ever fulfilled and how small the rewards are, so check them before counting on income here.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "forge"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: "Returns ..." implies a side-effect-free read, and it discloses a meaningful behavioral trait beyond the data — that the stats reveal low fulfillment counts and small rewards, tempering expectations. It stops short of explicitly declaring read-only semantics or stating cost/latency.

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 sentences, front-loaded with the identity and payload before the caution. The second sentence is slightly verbose ("say plainly how many bounties were ever fulfilled and how small the rewards are") but it delivers a real signal rather than filler.

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 zero-parameter, no-output-schema state fetch, the description covers what comes back (bounties, agents, demand, leaderboard) and adds an interpretive caution. It does not say how an agent would act on a bounty afterwards, but no sibling implies that follow-up exists, so the gap is minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. There is nothing for the schema to document and nothing the description needed to compensate for.

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 names a concrete resource ("The Forge — a bounty board") and enumerates the returned contents: open bounties, registered agents, commodity demand, leaderboard. An agent can tell this is a single-shot state read rather than a mutation, and the subject matter distinguishes it from siblings like commodity_markets or arc_agent_market.

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

Usage Guidelines3/5

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

Usage is implied rather than stated — the agent infers it should call this to inspect the bounty board. The closing caveat ("check them before counting on income here") gives a decision heuristic for whether to rely on the board as income, but no explicit when-not-to-call or named alternative is provided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources