Skip to main content
Glama

Search the hub

hub_search

Search published single-question judgment cards by title, author, domain, type, or locale to locate public test cases and get versioned refs for retrieval or forking.

Instructions

Search published single-question judgment cards (rubrics with public test cases). Returns one result per card at its newest version, with a hub:owner/slug@rv_… ref for hub_get or fork_rubric.

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

Input Schema

NameRequiredDescriptionDefault
qNomatches title, author, slug and domain
hubNo
typeNonoul = yes/no
limitNo
ownerNo
domainNo
localeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations, so the description carries the full load. It usefully discloses deduplication semantics (one result per card at its newest version) and the exact ref format returned, which is genuinely beyond the schema; however it says nothing about ordering, pagination (limit caps at 50), total counts, or auth, which matter for a search 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 tight sentences, zero filler, with the resource definition front-loaded and the actionable output/ref information second. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 does well to describe the shape of results (one row per card, newest version, ref included). But for a 7-parameter search tool with no annotations and thin schema coverage, it leaves filtering behavior, result ordering, and pagination unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 29% across 7 parameters, so the description needed to compensate and does not: it never explains q matching semantics, what `hub`, `owner`, `domain`, or `locale` filter on, or how limit affects results. Only the `noul = yes/no` enum meaning is documented, and that is in the schema, not the description.

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?

Names a specific verb (Search) and a precisely scoped resource: published, single-question judgment cards, defined inline as rubrics with public test cases. It also implicitly separates itself from hub_get by stating that results carry a `hub:owner/slug@rv_…` ref intended for hub_get or fork_rubric.

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?

Usage is only implied: an agent can infer this is the discovery step before hub_get or fork_rubric. There is no explicit when-to-use or when-not-to-use guidance, and no comparison against list_rubrics or search alternatives, so the agent must infer the routing itself.

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