There's An AI For That

List feature tools

list_feature_tools

Read-only

List every AI tool on one TAAFT feature, in the same order as the feature page. This is a complete listing, not a search: no query, no relevance ranking, nothing missing and nothing extra. Each tool carries the full get_tool fields, including deal details when an approved TAAFT partner offer exists. Preserve returned URLs exactly.

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": {
      "feature": "<feature>"
    },
    "name": "list_feature_tools"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size. Keep calling with next_offset until has_more is false to get the complete listing.
`offset`	No	Number of tools to skip, in feature page order.
`feature`	Yes	Feature id, feature slug, or exact feature name as returned by list_features.

Output Schema

Name	Required	Description	Default
`limit`	Yes
`tools`	Yes
`total`	Yes
`offset`	Yes
`feature`	Yes
`has_more`	Yes
`next_offset`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, so the bar is lower, yet the description still adds ordering semantics (feature-page order), completeness guarantees, and the fact that deal details are included for approved partner offers. The 'Preserve returned URLs exactly' instruction is a genuine output-handling caveat not derivable from the schema.

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?

Four short sentences, front-loaded with purpose, then differentiation, then output content, then an output-handling caveat. Every sentence carries distinct information; no filler.

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?

An output schema exists so return values need not be enumerated, yet the description still tells the agent what to expect (full get_tool fields, deal details). Pagination is covered by the schema. Nothing needed to call this correctly is missing.

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 description coverage is 100% and the schema already documents limit/offset/feature including pagination guidance, so the baseline is 3. The description adds only the ordering context for offset ('same order as the feature page'), which is marginal but real.

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?

States a specific verb and resource ('List every AI tool on one TAAFT feature') and immediately differentiates itself from the search siblings ('This is a complete listing, not a search: no query, no relevance ranking'). An agent can distinguish it from search_tools and list_feature_models without opening any schema.

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?

Explicitly frames the usage context: use this for a complete, ordered enumeration rather than a query-driven lookup. It does not name the concrete alternative (search_tools) or state when-not to use it, but the exclusion of querying and ranking gives clear routing signal.

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

All There's An AI For That tools Inspect

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.