Skip to main content
Glama
Sign In
Algora MCP Server

Algora MCP Server

by idapixl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_bounty_stats

Get aggregate statistics on open bounties: total count, combined value, average amount, and breakdowns by tech stack and organization to understand the overall bounty landscape.

Instructions

Get aggregate statistics about open bounties: total count, combined value, average amount, breakdown by tech stack, and breakdown by organization. Useful for understanding the overall bounty landscape.

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_bounty_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoScope stats to a specific org slug. Omit for all orgs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Without annotations, the description must disclose behavior. It accurately describes a read-only aggregation operation with no side effects. However, it omits potential details like authentication or rate limits, which are not critical for this stat tool.

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 concise sentences: the first summarizes the tool's output, the second its utility. No extraneous information.

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?

Despite no output schema, the description enumerates all key statistics returned (count, value, average, breakdowns), making the tool's output fully predictable.

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?

The schema already describes the single optional parameter 'org' with clear semantics. The tool description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 clearly states it retrieves aggregate statistics about open bounties and lists specific metrics (count, value, average, breakdowns), effectively distinguishing it from sibling tools that focus on individual bounties.

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?

The description notes it is 'useful for understanding the overall bounty landscape,' implying use for high-level statistics rather than specific bounties. It could explicitly state when not to use it, but the context is clear.

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

Deploy Server

Other Tools