Skip to main content
Glama

Ego Agent Marketplace

Search paid APIs

search_services
Read-onlyIdempotent

Find paid APIs on the Ego Agent marketplace. Free, read-only. Returns each API's id, price in USDC, who runs it and how many paid calls it has had. Leave query empty to list everything.

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

Input Schema

NameRequiredDescriptionDefault
queryNoWords to look for in the name, description or category.
categoryNoOnly this category.
first_party_onlyNoOnly the APIs Ego Agent runs itself.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful context beyond the annotations by stating the tool is free and by naming the returned fields and the empty-query list-all behavior, though it does not mention pagination or result ordering.

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?

The description is three short sentences, front-loaded with what the tool does, followed by safety and return-value context. Every sentence adds useful information without repetition.

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?

There is no output schema, so the description appropriately lists the key returned fields: id, price, operator, and paid-call count. It is nearly complete for a search tool, with only minor gaps around ordering and pagination.

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 100%, so the schema already explains all three parameters. The description adds meaningful behavior beyond the schema by clarifying that an empty query returns everything, which is not stated in the query parameter's schema description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 paid APIs on the Ego Agent marketplace. It also scopes the result to discovery of APIs, making it distinguishable from get_service, which is likely a detail lookup rather than a search.

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?

The description gives clear context for discovery searches and specifies that an empty query lists everything. It does not explicitly say when to use this instead of a detail-oriented sibling such as get_service, but the search purpose is clear.

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