Skip to main content
Glama
Sign In

HiveRef

by com.hiveref
OverviewDiscussionsAdmin

Find reference checks

list_recent_checks
Read-onlyIdempotent

Finds the organisation's reference checks, newest first, with candidate name, role, status, how many referees have responded and a link to the check in HiveRef. Can filter by candidate name, role title or status. Results are paged: has_more and next_offset show when there are more checks.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many checks to return, 1 to 50. Default 20.
offsetNoSkip this many results, for the next page (next_offset from the previous page).
statusNoOnly return checks with this status. invites_pending and in_progress mean waiting on referees; completed means all referees responded.
role_titleNoOnly checks whose role title contains this text, for example "warehouse".
candidate_nameNoOnly checks whose candidate's name contains this text, for example "Sam" or "Whitfield".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: default ordering, the returned summary fields, and explicit pagination via has_more and next_offset, which an agent needs in order to loop pages correctly.

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 tight sentences: purpose and ordering first, then filters, then pagination behavior. No filler, no repetition, and the most decision-relevant information is front-loaded.

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?

With no output schema, the description carries the burden of explaining what comes back, and it does: candidate name, role, status, referee response counts, a HiveRef link, plus has_more/next_offset for paging. For a five-optional-parameter read tool with full schema coverage and complete annotations, nothing material is missing.

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?

Schema description coverage is 100%, so limit, offset, status, role_title and candidate_name are already fully documented, including enum meanings and examples. The description restates the three filters and pagination without adding syntax or semantics beyond the schema, so the baseline 3 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 verb and resource ('Finds the organisation's reference checks') plus ordering ('newest first') and the exact fields returned, so an agent knows precisely what this returns. It also implicitly separates itself from list_completed_checks by describing a general, status-filterable listing rather than a completed-only one.

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?

The description explains what can be filtered (candidate name, role title, status) and that results are paged, which implies the browsing/search use case. It never states when to prefer this over list_completed_checks or get_check for a single record, and gives no exclusions or prerequisites.

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

All HiveRef toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources