Aident AI

Search Aident apps and actions

capabilities_search

Read-only

Search capabilities only when an exact canonical Action name is not already known. Action results use canonical names; copy the exact returned name into capabilities_get, capabilities_preflight, and capabilities_execute.

Input Schema

Name	Required	Description
`mode`	No	Search mode (default: hybrid)
`limit`	No	Max results (default: 20)
`query`	No	Single search query
`scope`	No
`types`	No	Filter by type (default: all capabilities). Use action for integration-backed Actions.
`offset`	No	Pagination offset (default: 0)
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`queries`	No	Batch search queries
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`skillType`	No	@deprecated Prefer types: ["action"] or types: ["skill"]. Deprecated persisted values are accepted.
`targetEnv`	No	Target environment (default: current)
`bypassCache`	No	Bypass cache and force fresh search (default: false)
`enabledOnly`	No	Filter integrations by enabled status (default: true)
`skillStatus`	No	Filter skills by status (default: active)
`allowLeadingWildcard`	No	Allow leading wildcards (default: false)
`allowedIntegrationIds`	No	Security boundary: only return skills where required_integration_ids are a subset

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 14, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}

addedInput schema / required

Added value: +[
+  "context",
+  "llm_model"
+]

Changed1 schema field changedAug 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}

First observedAug 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false). The description adds meaningful behavioral context the annotations don't: results carry canonical names that must be reused verbatim downstream. It stops short of disclosing pagination or caching behavior, but those are partly reflected in 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?

Two tight sentences with zero waste. The usage constraint is front-loaded ahead of the workflow instruction, so the most decision-relevant information comes first.

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?

With an output schema present and 94% schema coverage, the description needn't explain return values or every parameter. It covers the routing decision and downstream usage well; the only minor gap is not mentioning search modes or batch-query behavior, which the schema handles.

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 94%, so the schema already documents nearly every parameter (mode, limit, types, offset, scope, etc.). The description adds no parameter-level syntax or format detail beyond the schema, so the baseline 3 is appropriate.

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 capabilities") and its title clarifies scope (apps and actions). It explicitly distinguishes itself from sibling tools by naming capabilities_get, capabilities_preflight, and capabilities_execute as downstream consumers of its results.

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 an explicit gating condition ("only when an exact canonical Action name is not already known") plus a concrete workflow: copy the returned canonical name into get/preflight/execute. This tells the agent both when to call it and what to do with the output, leaving nothing to inference.

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

All Aident AI tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?