Skip to main content
Glama

Sato Hub: Build Onchain & Crypto Agents

by ai.satohub
OverviewDiscussionsAdmin

Inspect one published agent package

onchain_agent_inspect_listing
Read-onlyIdempotent

USE WHEN you have a PACKAGE slug (from onchain_agent_search_listings) and need what it does, what it needs and what is on record about it before recommending a download or fork. NOT FOR directory listings such as a framework, MCP server or project (use onchain_agent_get_resource instead) or finding a package slug (use onchain_agent_search_listings).

RETURNS the package's public fields only: task, description, creator display name, version digest and signing state, recipe, input/output schemas, required services and permissions, model support ("configured, not evaluated"), operating-cost basis as the creator wrote it, license and whether fork is permitted, support, evidence freshness for this digest, integrity, and acquisition modes (download, fork — there is no deploy or buy), and superseded_by (the template that replaces the package, or null).

PACKAGES VS DIRECTORY: packages are agents published through Sato Hub, a separate set from the directory of projects and tools. A directory slug answers "directory listing, not a package".

RULE ENFORCED: never a signed URL, account id or project id. "integrity: stale_evidence" means the stored artifact no longer matches the seal and download is withheld. Cite sato_url. manifest_url is the public signed release manifest a downloader checks the zip against offline with /verify-release.mjs — it proves the bytes are what Sato sealed, not that they are safe. Read-only.

Example: call onchain_agent_search_listings first, then { slug: }

Input Schema

NameRequiredDescriptionDefault
slugYesThe package slug from onchain_agent_search_listings. This is NOT a directory slug: for a directory listing (a project, framework or tool such as coinbase-agentkit) call onchain_agent_get_resource instead.
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 / slug / description
      Previous value: -"The package slug from onchain_agent_search_listings."New value: +"The package slug from onchain_agent_search_listings. This is NOT a directory slug: for a directory listing (a project, framework or tool such as coinbase-agentkit) call onchain_agent_get_resource instead."
  3. 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."
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent safety, but the description adds substantive behavioral context beyond them: the rule enforced (never a signed URL, account id or project id), what 'integrity: stale_evidence' means (download withheld), the distinction between manifest_url proving bytes vs. safety, and the absence of deploy/buy modes. This is meaningful disclosure, not restatement.

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' and clearly sectioned (RETURNS, PACKAGES VS DIRECTORY, RULE ENFORCED), so an agent can scan it quickly. It is long, and the 'PACKAGES VS DIRECTORY' paragraph partly restates the earlier NOT FOR clause and the schema description, costing it the top mark.

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?

There is no output schema, so the description carries the return-value burden and does so thoroughly: it enumerates the public fields returned, the acquisition modes, and the superseded_by semantics. Combined with the safety and integrity notes, nothing needed to call or interpret the result 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 coverage is 100% and the schema already documents the slug's origin and its non-directory nature, so the description largely repeats structured content. It adds only the concrete example invocation, which is marginal; baseline 3 is appropriate when the schema does the heavy lifting.

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 (inspect) and resource (one published package) and immediately scopes it to a package slug. It names the siblings it is not (onchain_agent_get_resource for directory listings, onchain_agent_search_listings for finding slugs), so an agent can distinguish it without opening any 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?

Explicit 'USE WHEN' condition tied to a prerequisite (you already hold a package slug), plus a 'NOT FOR' clause naming both alternatives and the exact tool to use instead. Nothing 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.

All Sato Hub: Build Onchain & Crypto Agents 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