Skip to main content
Glama

Agenturo

Find public AI agents

find_agents
Read-onlyIdempotent

Search the public AI agents hosted on Agenturo by topic, job or name, for example "fact-checking", "nutrition coach" or "stoic philosophy". People, brands, products and businesses can have their own agent here, so a person's or company's name finds the agent that represents them, if there is one. Returns each agent's name, address (handle.agenturo.app), what it does and its topics. With no query, returns featured agents.

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
limitNoHow many agents to return (1–10, default 5).
queryNoTopic, job or name to search for — a person's, brand's or business's name finds the agent that represents them. Leave empty for featured agents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world semantics, so the bar is lower. The description adds real context beyond them: it discloses the return fields (name, handle address, description, topics) and the no-query fallback to featured agents, though it says nothing about result caps or pagination behavior.

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?

Front-loaded with the purpose, then examples, then the entity-name nuance, then return shape and the empty-query case. Dense and mostly waste-free, though the 'People, brands, products and businesses can have their own agent here…' sentence is slightly verbose for the point it makes.

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 two-optional-parameter read tool with full annotations and no output schema, the description is nearly complete: purpose, query semantics, defaults, and returned fields all appear. The only gap is that it doesn't mention that results are capped at 10 and how to explore further.

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%, so both parameters are already documented, giving a baseline of 3. The description reinforces query semantics with example searches and the entity-name behavior, but adds no new format rules beyond the schema's own wording ('Leave empty for featured agents' is essentially repeated).

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 the public AI agents hosted on Agenturo' — plus the facets it searches over (topic, job, name) and concrete example queries. An agent can distinguish this directory search from single-agent tools like get_agent, though no sibling is named explicitly.

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?

Clear usage context: use this to locate agents by topic, job, or a person/brand name, and 'With no query, returns featured agents' defines the empty-input behavior. It stops short of naming alternatives (e.g., get_agent for a known handle) or stating when not to use it.

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