Skip to main content
Glama
Sign In
hypernatt-terminal

hypernatt-terminal

by DIALLOUBE-RESEARCH
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

get_agent_manifest

Start here to discover available tools, prices, and trial status, then select the right crypto workflow for your task.

Instructions

Start here (free): 5 tools, prices, daily per-tool/per-token trial status and intent-based journeys. Choose liquidation radar, native BTC/ETH depth, Li.Fi swap or the L2 archive catalog. Compact includes arguments; detail=full adds quota/pass/onboarding.

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

Input Schema

NameRequiredDescriptionDefault
detailNoDefault compact. full = quota/pass/onboarding.
localeNoNot a translation switch. Ignored. Catalog is English only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.11
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed2 schema fields changedv1.0.10
    • addedInput schema / properties / detail
      Added value: +{
+  "description": "Default compact. full = quota/pass/onboarding.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / locale / description
      Previous value: -"en or fr (default en)"New value: +"Not a translation switch. Ignored. Catalog is English only."
  3. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does reasonably well: it states the call is free, that trial status is refreshed daily per tool/token, and that detail=full expands the payload to quota/pass/onboarding. It does not explicitly say the call is read-only or comment on response size, which is the remaining gap for a zero-annotation tool.

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?

Three short sentences, front-loaded with the 'Start here (free)' hook and the content inventory, then the mode difference. Some enumerative marketing flavor ('native BTC/ETH depth') is denser than needed but still conveys the catalog contents.

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?

For a zero-required-parameter, no-output-schema discovery tool, the description enumerates what comes back (tools, prices, trial status, journeys) and the compact-vs-full distinction. It stops short of describing the return structure or size, which matters slightly more since no output schema exists to cover it.

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 defines detail's enum and describes full as quota/pass/onboarding, so the description mostly restates that. It adds one genuinely new detail — that compact includes arguments — but nothing about locale beyond what the schema's 'Ignored' note already covers. Baseline 3 is appropriate.

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?

The description identifies this as an entry-point manifest tool that surfaces 5 tools, prices, daily trial status and intent journeys. It names the sibling offerings (liquidation radar, native depth, Li.Fi swap, L2 archive) so an agent can distinguish this catalog from the operational tools. It lacks a crisp verb+resource phrasing ('Start here' is an instruction rather than a statement of what is returned), keeping it short of a 5.

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

Usage Guidelines4/5

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

'Start here (free)' gives an explicit trigger for calling this first, and the sentence about choosing among radar/depth/swap/archive implicitly frames this as the discovery step before those siblings. It does not state exclusions or when to skip straight to a sibling, so the routing guidance is directional rather than complete.

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