Skip to main content
Glama

Omakase Box — Delegate Coding Tasks, Solve Bounties

The board in numbers

get_numbers
Read-onlyIdempotent

The board as a whole, to decide whether it is worth checking: whether merged rewards were recorded paid, what is owed now, how much pays on merge, what was posted and merged in the last 30 days, open rewards with no attempt yet, pull requests by others, solvers and days to a decision. Each group says what it counts. Facts, not a rating.

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": "get_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and closed-world, so the bar is lower. The description still adds real value beyond them: it discloses that the response is grouped counts, that each group is self-describing ("Each group says what it counts"), and that it reports facts without a rating or score. It does not describe format or magnitude, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and there is no filler, but the middle sentence is a dense, comma-spliced list of metrics ("what is owed now, how much pays on merge... solvers and days to a decision") that is harder to scan than a short bulleted set of groups. It is compact but not well structured for an agent parsing the return categories.

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 no-argument, read-only aggregate with no output schema, the definition covers what matters: the scope of the aggregation, the categories of counts returned, and the fact that no evaluative score is produced. Only the exact shape/format of the groups is left unstated, which is a minor gap for a summary tool.

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 there is nothing for the description to disambiguate; the baseline of 4 applies. No parameter meaning is lost or misrepresented.

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 the resource scope explicitly ("the board as a whole") and enumerates the metric groups it aggregates, which implicitly separates it from the per-item siblings get_bounty and find_bounties. The verb is only implied ("get"), and the run-on enumeration makes the exact scope harder to parse than a clean 'returns aggregate counts for X, Y, Z' statement would.

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?

"To decide whether it is worth checking" gives a triage/overview use case, which is genuine guidance. But it never states when NOT to use it or names find_bounties/get_bounty as the follow-up when the overview indicates something worth investigating, so the routing is only implied.

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.