Skip to main content
Glama
Sign In

Ahel

by ai.ahel
OverviewDiscussionsAdmin

Search data tasks and provider tools

capability_search
Read-onlyIdempotent

Search Ahel's catalog of data tasks and provider tools by words, a task id or a tool id: company and people enrichment, SEO, social, ads, e-commerce, reviews, AI generation, market and public data. Each result has its genuine task id or tool id, its platform, its status (ready, coming_soon meaning temporarily unavailable because Ahel has no provider for it yet, or unavailable while the run service is down) with the exact reason; a temporarily unavailable result may carry a market price seen elsewhere, for comparison. The same catalog, ids and statuses as the Catalog page on ahel.ai. Describe the job in plain words; results are ranked by how well they fit. When nothing fits it answers verdict none with the three nearest items: then call catalog_request. Free; changes nothing. NOT for: one item's exact inputs and prices, which is capability_inspect, or the team's own tools, which is my_tools.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOptional: only tasks or only provider tools.
limitNoHow many results, 1-50. Default 10.
queryNoWords to match, or an exact task id (companies.enrich) or tool id.
statusNoOptional: only items in this state.
platformNoOptional platform id (companies, google, image-gen): only its items; with no query, its whole shelf.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "ready",
-  "needs_connection",
-  "coming_soon",
-  "unavailable"
-]New value: +[
+  "ready",
+  "coming_soon",
+  "unavailable"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, but the description adds meaningful context about status semantics (ready, coming_soon, unavailable with exact reasons), ranking logic, and the comparison price shown for temporarily unavailable results. It does not cover pagination or rate limits, which are minor gaps given the annotations.

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 description is long but well-structured and front-loaded, with the core purpose first and exclusions last. Almost every sentence earns its place by clarifying scope, statuses, or fallbacks, though the reference to the Catalog page feels slightly redundant.

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

Completeness5/5

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

There is no output schema, yet the description explains the shape and key fields of each result (id, platform, status, exact reason, optional comparison price) and the fallback verdict. Combined with the usage guidance and exclusions, an agent has everything needed to call and interpret this tool.

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 baseline is 3, but the description adds useful meaning beyond the schema: the query can be a plain-language job description or an exact task/tool id, and results are ranked by fit. It does not expand on all parameters individually, but the added context is valuable.

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 (search Ahel's catalog of data tasks and provider tools) and enumerates the domains it covers. It also explicitly names what it is not (capability_inspect, my_tools), making it easy to distinguish from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance ('Describe the job in plain words'), defines fallback behavior when nothing matches ('verdict none ... then call catalog_request'), and includes a clear NOT-for section pointing to the right alternative tools.

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

All Ahel toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources