Highwire

Search coins

search_coins

Read-onlyIdempotent

Locate higher.fun coins by name, ticker, or mint address to research tokens and check rug risk before trading.

Instructions

Find higher.fun coins by name, ticker or mint address.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_coins"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Name, ticker or mint

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

B3.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond them: it does not say how many results come back, whether matching is fuzzy or exact, whether results are ranked, or what happens with an unknown ticker.

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?

One short sentence, front-loaded with the verb and resource, with zero filler. Nothing can be trimmed without losing information.

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 one-parameter read-only search the definition is serviceable, and annotations cover safety. However, with no output schema the description should say that it returns a collection of matching coins (and roughly how matching behaves), which it omits.

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?

With 100% schema description coverage and a single required query parameter documented as 'Name, ticker or mint', the schema carries the semantics. The description only restates those same three key types, adding no format hints such as whether a partial name or a case-insensitive ticker works.

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 names a specific verb (find) and resource (higher.fun coins) and enumerates the three lookup keys (name, ticker, mint address). It is clear on its own, but it never distinguishes itself from close siblings like list_coins, get_coin or check_ticker, so an agent must infer which of these applies.

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

Usage Guidelines3/5

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

Usage is only implied: search when you have a partial identifier rather than an exact coin id (which would point to get_coin). There is no explicit when-to-use, when-not-to-use, or named alternative, and nothing says what to do when multiple or zero matches occur.

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