Skip to main content
Glama

Search projects

naut_search_projects
Read-only

Search and filter crypto projects. Supports q, page, limit. Costs 5 credits.

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

Input Schema

NameRequiredDescriptionDefault
qNoText to match against names, handles and domains.
pageNoPage number, from 1.
sortNo
limitNoRows per page, 1 to 100. Default 30.
tokenNolaunched = has a token, pre = no token yet.
sectorNoOnly projects in any of these sectors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-annotation context: calls cost 5 credits. It does not describe pagination totals, result ordering, or match semantics, which would matter for a search endpoint.

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 purpose, then fields, then cost. The parameter list partially duplicates the schema, which is minor waste, but nothing is padded or buried.

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 six-optional-parameter search with no output schema, the definition covers purpose, cost and a few parameters. It leaves unaddressed what a result set contains, how total pages are surfaced, and whether matching is fuzzy or exact, which an agent would want before paging through credits.

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 83%, above the threshold where the schema is doing the documentation work, so a 3 is the baseline. The description names q, page and limit but omits sort, token and sector, and adds no filtering semantics beyond what the schema already says.

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?

States a specific verb and resource: 'Search and filter crypto projects.' The resource is named explicitly, which separates it from the sibling search tools for investors, people and services. It stops short of an explicit contrast with 'naut_search', but an agent can still route on the resource noun.

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?

No when-to-use or when-not-to-use guidance is offered, and no alternative is named. The only decision aid is the cost line, which tells the agent a call is expensive but not why this tool should be chosen over 'naut_search' or the typed sibling searches.

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.

Resources