Skip to main content
Glama
Sign In
ASTRO

ASTRO

by jarvisways-cyber
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

astro_get_started

Read-onlyIdempotent

Explains how to access ASTRO's crypto intelligence without signup, credentials, or trial activation, so users can start exploring public data immediately.

Instructions

Explain public access; no signup, credentials or trial activation needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful auth context by stating no signup, credentials, or trial activation are needed, but it does not describe output format or any other runtime behavior.

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?

The description is a single short sentence with no filler. It is front-loaded with the intended action ('Explain public access'), though the terse phrasing leaves the action somewhat ambiguous.

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?

For a no-parameter, non-destructive informational tool with no output schema, the description covers access requirements but not what the tool actually returns or how it should be used in an agent workflow. It is minimally adequate but misses useful context.

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?

The tool takes zero parameters, so there are no parameter semantics for the description to clarify. The schema is an empty object, and the baseline for zero-parameter tools applies.

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

Purpose3/5

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

The description says 'Explain public access' and adds an access constraint, but it does not clearly state what the tool returns or how it differs from siblings astro_signal, astro_context, or astro_basket. The purpose is vaguely inferable as an onboarding or public-access explanation tool, but not specific enough for confident selection.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives. The statement about no signup or credentials gives a usage condition only indirectly, but it does not say when this tool is preferred over the sibling tools.

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

Deploy Server

Other Tools