Skip to main content
Glama

CoinBucha

by com.coinbucha

Bitcoin hiring velocity

get_hiring_signal
Read-onlyIdempotent

Hiring velocity across tracked Bitcoin and crypto-infrastructure employers, counted from their live ATS boards. Returns { as_of, companies[], note, why, disclaimer }; each company carries company, ticker, category, ats, careers_url, open_roles, open_roles_30d_ago, open_roles_90d_ago and the derived delta_30d, delta_90d and pct_30d. Example: {"company": "coinbase"} for one employer, or {} for every employer tracked. When a company filter matches no tracked employer the response adds coverage_note and tracked_count, saying that the name is outside the tracked set — a limit of coverage, not a finding about whether that company is hiring. Information, not financial advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyNoCase-insensitive company filter

TDQS

A4.7/5.0
Behavior5/5

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

The description goes beyond the annotations by disclosing the full response shape (as_of, companies[], note, why, disclaimer), the per-company fields including derived deltas, and the special coverage_note/tracked_count behavior when no tracked employer matches. It also includes the financial disclaimer.

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?

Three sentences pack purpose, response format, example, edge case, and disclaimer. Each sentence adds value, front-loading the core purpose. No fluff or repetition.

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?

Given no output schema exists, the description thoroughly covers the return structure and edge cases, making it complete for an agent to understand what will be returned and how to interpret the data. The note about coverage limits is particularly valuable.

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 schema already covers the single parameter well with 'Case-insensitive company filter'. The description adds a concrete example using {"company": "coinbase"} and clarifies the empty-filter behavior, providing practical usage guidance beyond the schema.

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 specifies the exact resource ('tracked Bitcoin and crypto-infrastructure employers') and the measurable ('hiring velocity'), distinguishing it clearly from sibling tools like etf_flows or treasury_holdings. The verb 'counted from their live ATS boards' adds precision.

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?

Provides clear context on when to use (for hiring velocity data) and how to filter via the optional company parameter, including the no-match behavior. It does not explicitly name alternative tools or state when not to use, but the context is unambiguous.

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

All CoinBucha toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool targets a distinct Bitcoin intelligence domain—ETF flows, hiring, hashrate, sovereign reserves, treasury holdings, daily digest, and cross-signal scan—with no functional overlap. Even similar-sounding holdings tools are clearly separated by nation-state vs. corporate focus.

Naming Consistency4/5

Six of seven tools follow a consistent get_<domain> pattern, making them predictable and discoverable. The single outlier, scan_signals, breaks the pattern slightly but remains readable and within the same verb_noun style.

Tool Count5/5

Seven tools is well-scoped for a Bitcoin signals server—broad enough to cover multiple indicator categories without bloat. Each tool serves a clear, non-redundant purpose.

Completeness5/5

The tool set covers the stated domain of leading non-price indicators comprehensively, including individual domain-specific queries and an aggregated, filterable scan. No obvious missing operations or dead-ends; the daily brew provides a digest while scan_signals offers detailed rankings.

Resources