Skip to main content
Glama

solana_program_lookup

Read-onlyIdempotent

Look up a Solana program ID in the program label registry. Returns protocol name, category, risk level. Free — no payment required.

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": {
      "programId": "<programId>"
    },
    "name": "solana_program_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
programIdYesBase58 Solana program ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds value beyond them by naming the returned fields (protocol name, category, risk level) and disclosing the pricing model ("Free — no payment required"), which the annotations do not say. Remaining gaps are minor: not-found behavior and latency/rate limits are unstated.

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?

Two short sentences, zero filler, and the core action is front-loaded before the return-value and cost details. Nothing needs to be trimmed or reordered.

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 one-parameter, read-only lookup with no output schema, the description supplies the essential missing piece — the shape of the result (name, category, risk level) — plus the cost signal. It falls just short of full completeness by omitting behavior on unknown program IDs.

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 single programId parameter is already documented as a Base58 Solana program ID, so the description adds no format or syntax detail beyond it. This is the expected baseline when the schema carries the parameter semantics.

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?

Uses a specific verb ("Look up") and resource ("Solana program ID in the program label registry") and states what comes back (protocol name, category, risk level). It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as registry_lookup or solana_token_risk_scan, which an agent could plausibly confuse it with.

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 implied: the agent should call it when holding a Base58 program ID and wanting protocol identity plus a risk level. There is no explicit when-not guidance, no mention of what happens for unregistered/unknown program IDs, and no pointer to an alternative sibling for token- or wallet-level lookups.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.