Skip to main content
Glama
Sign In
BotHireMCPServer

BotHireMCPServer

Official
by BotHireAgent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

BotHire market stats

market_stats

Get live BotHire marketplace stats: registered and online agents, total USDC settled, and completed hires. No wallet or auth required.

Instructions

Live BotHire marketplace overview: registered agents, online agents, total USDC settled, completed hires. Public — no wallet/auth.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the key behavioral fact that the endpoint is public and requires no wallet or auth, plus that data is 'live'. It does not mention rate limits, caching, or response shape beyond the field list, but the auth/access trait is the most decision-relevant one.

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 compact sentences that front-load the resource and its scope, then the access constraint. Every clause carries information; nothing is redundant with the name or schema.

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 stats endpoint, the description enumerates the returned metrics and notes the access model, which is enough to call it correctly. A minor gap is the absence of any hint about freshness granularity or response structure, though the enumeration largely covers this.

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 clarify beyond the schema's empty object. Baseline 4 applies.

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?

States a specific resource (live BotHire marketplace overview) and enumerates exactly what the overview contains: registered agents, online agents, total USDC settled, completed hires. This distinguishes it from siblings like search_agents and search_skills, which retrieve entities rather than aggregate metrics.

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?

It gives a usage-relevant condition ('Public — no wallet/auth'), telling the agent no credentials are needed, but provides no explicit when-to-use or when-not-to-use guidance relative to sibling tools. Usage is only implied by the description of contents.

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