Skip to main content
Glama

Sato Hub: Build Onchain & Crypto Agents

Check what a crypto agent skill does before installing it

onchain_agent_search_skills
Read-onlyIdempotent

USE WHEN someone is about to install an agent skill and should know what it will touch first: keys, credentials, remote scripts, outbound hosts. Crypto-relevant agent skills from ClawHub and skills.sh, each with a static DISCLOSURE: hosts it contacts, whether it generates or handles private keys, whether it asks the user to paste a credential, whether it pipes a remote script into a shell, whether it grants itself unrestricted tools, whether it registers the agent with a third-party host, whether it schedules itself. Each flag carries evidence lines on the skill's page. NOT FOR finding frameworks, MCP servers or wallets (use onchain_agent_search_resources instead), an npm/pip/MCP install command (use onchain_agent_check_install), or one skill's Preflight verdict (use onchain_agent_preflight with skill).

RETURNS (json): { total, skills: [{ id, name, registry, canonical_url, installs, stars, disclosure_flags, hosts_contacted, declared_env, registry_scan, belongs_to_slug, skill_md_sha256, as_of }], note }.

A disclosure is a description, not a safety verdict — a wallet skill that generates keys is doing its job, and no flags is not a clearance. The registry's own scan status is attributed to the registry. slug is the directory listing a skill targets: a slug that matches no skill comes back empty, and says whether it is a directory listing (onchain_agent_get_resource reads it), a wiki page or Sato Hub's own planner. Read-only. Cite https://satohub.ai/skills.

Examples:

  • "solana skills that don't touch keys" -> { query: "solana" } then filter disclosure_flags

  • "which skills phone home" -> { flag: "registers_with_third_party" }

  • "skills for Coinbase AgentKit" -> { slug: "coinbase-agentkit" }

Input Schema

NameRequiredDescriptionDefault
flagNoOnly skills carrying this disclosure flag: pipes_remote_to_shell, executes_fetched_code, generates_or_handles_keys, solicits_credentials, reads_secret_paths, broad_tool_grant, registers_with_third_party, schedules_persistence.
slugNoOnly skills that target this directory listing.
limitNo
queryNoFree text over skill name, description, owner/repo and hosts contacted.
registryNoRestrict to one registry.
response_formatNoText format; structuredContent is JSON either way.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • changedInput schema / properties / response_format / description
      Previous value: -"Output format: 'markdown' (human-readable, default) or 'json' (machine-readable)."New value: +"Text format; structuredContent is JSON either way."
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive/openWorld, and the description still adds real behavioral context: a disclosure is a description not a safety verdict, no flags is not a clearance, the registry scan is attributed to the registry, and an unmatched slug returns empty with a note about what the slug actually is. That is genuine value beyond the structured fields.

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

Conciseness4/5

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

Front-loaded with USE WHEN / NOT FOR / RETURNS before caveats and worked examples, so the important routing information arrives first. It is on the long side and the RETURNS block plus caveats could be trimmed slightly, but nearly every sentence carries selection or invocation signal.

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 supplies the full JSON return shape, the meaning of each disclosure flag class, the citation requirement, and three worked query examples. For a six-parameter search tool this leaves nothing an agent needs in order to call it correctly.

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?

Schema coverage is already 83% and documents flag, slug, query, registry and response_format, so the baseline is 3. The description goes further by explaining slug's directory-listing semantics and the empty-result/fallback behavior, and by tying query to hosts contacted, which the schema does not.

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 (searching crypto-relevant agent skills) with the exact scope: static disclosure flags for skills about to be installed. It explicitly distinguishes itself from onchain_agent_search_resources, onchain_agent_check_install, and onchain_agent_preflight by name, so an agent can route without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Leads with an explicit USE WHEN trigger (about to install a skill and need to know what it touches) and a NOT FOR clause that names three alternative tools and the condition selecting each. Nothing about when to pick this over its siblings is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.