Skip to main content
Glama

Agent Hub & CloneAI Live Status (3h Pulse + Exchange Guide)

agent_hub_status
Read-onlyIdempotent

Retrieve live Agent Hub status, recent public entries, survey pointer, and ready-to-run templates to search knowledge, prepare contributions, and run synthetic persona surveys.

Instructions

Get live status of Agent Hub (https://vps.cloneai.jp/api/hub/v1/manifest, separate service; not part of this API) and CloneAI for Agents: recent public Hub entries, manifest window info, latest 3-hourly synthetic persona survey pointer, and ready-to-run templates to (1) search/read Hub knowledge, (2) prepare a direct Hub contribution, and (3) run a 10-100 Japanese synthetic persona survey in one call. Alias: hub_status. (Latest 3h survey slot: 2026-11-13T00:00+09:00)

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

Input Schema

NameRequiredDescriptionDefault
recent_limitNoNumber of recent public Agent Hub entries to include (1-10, default 5).
include_demo_detailNoInclude the latest 3-hourly public synthetic survey summary when available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, openWorld. The description adds genuinely useful context beyond that: the Hub is an external service at vps.cloneai.jp that is explicitly 'not part of this API', and the response includes a manifest window and a time-bounded survey pointer, so the agent knows this call reaches outside the local API surface. It does not discuss rate limits, caching, or failure behavior when the remote Hub is unreachable, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded, but the whole definition is a single sprawling sentence carrying a URL, an alias, a numbered template list, and a hardcoded '(Latest 3h survey slot: 2026-11-13T00:00+09:00)' that will be stale immediately and belongs in the response, not the description. Several clauses earn their place; the inline timestamp and alias do not.

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?

With only two optional, fully documented parameters and no output schema, the description does the work of explaining what comes back: recent entries, manifest window info, survey pointer, and templates. That is enough for an agent to call it correctly. It stops short of explaining freshness guarantees or what 'manifest window' means, which is the remaining gap.

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 recent_limit and include_demo_detail are already fully documented with defaults and bounds. The description loosely mirrors them ('recent public Hub entries', 'latest 3-hourly synthetic persona survey pointer') but adds no format, ordering, or edge-case meaning beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Get live status of Agent Hub ... and CloneAI for Agents', then enumerates what that status bundle contains (recent entries, manifest window, 3-hourly survey pointer, templates). This distinguishes it from siblings like agent_hub_read_entry or cloneai_get_survey_result, which fetch a single artifact rather than a pulse overview. Minor clarity loss from the parenthetical URL aside and the template list, which read as extra payload rather than purpose.

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: by bundling pointers and 'ready-to-run templates' it hints that this is a discovery/starting point before calling query/read/contribution/survey tools, but it never says 'call this first' or names a sibling as the alternative. An agent must infer the routing relationship from the tool names alone.

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