Skip to main content
Glama

Sato Hub: Build Onchain & Crypto Agents

by ai.satohub
OverviewDiscussionsAdmin

Check one project in detail

onchain_agent_get_resource
Read-onlyIdempotent

USE WHEN you need to judge one specific directory project: is it open source, still maintained, who is behind it, what does it support. NOT FOR a REGISTERED running agent (use onchain_agent_get_agent_passport instead), a published agent package (use onchain_agent_inspect_listing), install steps (use onchain_agent_get_deploy_spec), or finding a slug (use onchain_agent_search_resources first).

RETURNS (json): { resource: {...full record incl. marketplace + liveness fields}, recent_activity: [...], agent_docs } by slug, optionally with recent releases and posts. agent_docs is where the project's machine-readable docs are, each dated: { as_of, read_first, llms_txt, llms_full, docs_mcp, agent_card }, or null with agent_docs_reason (not_yet_archived, read_failed) when none is archived; null is not "no docs". An unknown or Deprecated slug is an error. Read-only.

Example: { slug: "coinbase-agentkit" }

Input Schema

NameRequiredDescriptionDefault
slugYesThe resource slug, e.g. 'coinbase-agentkit'.
response_formatNoText format; structuredContent is JSON either way.markdown
include_activityNoInclude the resource's recent activity feed (releases/posts).

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. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds useful behavioral detail beyond them: unknown or Deprecated slugs return errors, and agent_docs null has specific reasons rather than meaning 'no docs'. 'Read-only' is redundant with readOnlyHint, but the error and null semantics add real value.

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?

The description is well-structured with USE WHEN, NOT FOR, RETURNS, and Example sections, and the routing information is front-loaded. Despite its density, every section earns its place by clarifying selection, return shape, or error behavior; the only minor redundancy is restating 'Read-only'.

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 compensates by explaining the returned JSON shape, the meaning of agent_docs nulls, and error behavior for unknown/deprecated slugs. Combined with clear sibling exclusions and an example invocation, it is complete enough for an agent to call correctly.

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 the schema already fully documents slug, response_format, and include_activity. The description confirms slug usage via the example and notes optional recent releases/posts, which maps to include_activity, but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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?

The description states a specific action and resource: judging one specific directory project, with concrete dimensions (open source, maintained, who is behind it, what it supports). It also explicitly distinguishes itself from several named sibling tools, so an agent can route correctly without opening schemas.

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?

It provides explicit USE WHEN and NOT FOR guidance, naming alternatives for registering agents, inspecting listings, deploy specs, and slug discovery. This is exactly the when/when-not/alternatives structure that prevents tool confusion among many siblings.

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