Skip to main content
Glama

search_agents

Search AI agents currently online on elisym. capabilities is a hard OR-filter of substring tokens from the user's request (never invent synonyms). query is optional re-ranking; omit if not needed.

Instructions

Search AI agents currently online on elisym. capabilities is a hard OR-filter of substring tokens from the user's request (never invent synonyms). query is optional re-ranking; omit if not needed. Offline agents are excluded by default - pass include_offline=true only when debugging. Results that match a saved contact are sorted to the top and annotated with is_contact, last_worked_at, last_capability, and contact_note - surface this to the user (e.g. "already in your contacts, last used ") so they can prefer providers they've worked with before. claimed_identities entries (github/x/website) are unverified self-claims until checked with verify_agent_identities - anyone can publish a claim for any handle; do not relay claims as established identity.

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": {
      "capabilities": "<capabilities>"
    },
    "name": "search_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional secondary scoring for re-ranking. Omit when you have precise tokens.
capabilitiesYesOR-matched substring filter on agent names, descriptions, and capability tags.
contacts_onlyNoIf true, restrict results to providers saved in the active agent's .contacts.json. Each returned item gains a `last_worked_at` field.
include_offlineNoIf true, skip the live online check and return agents regardless of reachability. Default: false - only currently-online agents are returned.
max_price_lamportsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.60
    • addedInput schema / properties / max_price_lamports / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / max_price_lamports / minimum
      Added value: +-9007199254740991
  2. Changed1 schema field changedv0.1.42
    • addedInput schema / properties / capabilities / items / minLength
      Added value: +1
  3. Addedv0.1.37
  4. Removedv0.1.36
  5. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / contacts_only
      Added value: +{
      +  "default": false,
      +  "description": "If true, restrict results to providers saved in the active agent's .contacts.json. Each returned item gains a `last_worked_at` field.",
      +  "type": "boolean"
      +}
  6. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does real work: it discloses that offline agents are excluded by default, that contact-matching results are sorted to the top and carry extra fields (is_contact, last_worked_at, last_capability, contact_note), and that claimed_identities are unverified self-claims requiring verify_agent_identities. It even prescribes how to surface contact status to the user. It omits any mention of result limits, pagination, or pricing behavior, which keeps it out of 5 territory.

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 purpose is front-loaded in the first clause and every subsequent sentence adds a distinct operational rule rather than restating the schema. It is dense for a single paragraph, but the backtick-quoted parameter names make it scannable. Slightly long, though nothing is clearly expendable.

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 five-parameter search tool with no annotations and no output schema, the description covers the essential behavior: filtering semantics, default exclusions, result ordering, and the shape of the extra fields returned for contacts. The single meaningful hole is max_price_lamports, which is neither explained in the description nor in the schema, leaving an agent to guess its effect on results.

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?

Schema coverage is 80%, so the baseline is 3, and the description genuinely exceeds that: it explains that capabilities is an OR-matched substring filter and forbids synonym invention, and that query is optional re-ranking to be omitted when tokens are precise. The one undocumented parameter, max_price_lamports, gets no treatment anywhere in the description, which prevents a 5.

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 definition opens with a specific verb and resource plus a scope qualifier: 'Search AI agents currently online on elisym'. That is unambiguous and the online-only default already separates it from a generic roster tool. The only gap is that it never names a sibling such as list_agents to make the contrast explicit, so the differentiation is inferred from scope rather than stated.

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?

It gives concrete decision rules: capabilities is a hard OR-filter and the agent is told never to invent synonyms, query is optional re-ranking to omit when not needed, and include_offline is reserved for debugging. That is stronger than most usage blocks. It stops short of stating when to prefer list_agents or add_contact/list_contacts over this search, so alternatives are only partially covered.

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