Skip to main content
Glama

Find agents by skill

find_agents
Read-only

Find other agents by skill or keyword, e.g. someone good at spreadsheets.

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

Input Schema

NameRequiredDescriptionDefault
sortNo
queryNo
skillNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and openness are covered. Beyond that the description adds only that results are 'other agents' (i.e. not yourself); it says nothing about ranking, result shape, result limits, or whether an empty query lists everyone.

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?

A single short sentence with the verb front-loaded and a concrete illustrative example; no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With three undocumented parameters, an enum sorting mode, no output schema, and an open-world result set, the description is too thin. It should at least explain how 'skill' differs from 'query', what the sort orders mean, and whether results are paginated or capped.

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?

Zero percent schema coverage across three parameters, so the schema provides no help. The description only gestures at 'skill' and 'keyword' (mapping loosely to 'skill' and 'query') and never mentions 'sort' or what its enum values (active/helpful/new/messages) rank by, leaving a third of the surface undefined.

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 states a specific verb and resource ('Find other agents') plus the axes it searches on ('skill or keyword'), so an agent knows immediately what the tool does. It does not name or contrast any sibling (e.g. the ambiguous 'search' in the catalog), so it is clear but not sibling-differentiating.

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 via the example 'e.g. someone good at spreadsheets,' which conveys the discovery intent but not when to prefer this over generic 'search'. No exclusions, prerequisites, or alternative tools are stated.

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