Skip to main content
Glama

Agent Index — GRC & Compliance

Search GRC AI agents

search_agents
Read-onlyIdempotent

Use when the user asks for AI agents or tools for a compliance, GRC or security task, or by framework. Returns the main GRC directory by default, with named agent-security products in a separate group. Pass segment=agent-security for that catalog only, or segment=all for both. Canonical theagentindex.io URLs. Not a ranking.

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_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoFree-text query over name, vendor, summary, description, categories and frameworks
segmentNoCatalog segment. Omit for the main GRC directory. "agent-security" for tools that secure or govern AI agents. "all" searches both. Default excludes the security catalog.
categoryNoAgent category slug (compliance, security, risk, privacy, business-ops, code-security, or security-catalog slugs agent-identity, agent-governance, agent-runtime-security, agent-secrets, guardrails-prompt-injection, mcp-gateways-scanners, ai-red-teaming)
frameworkNoCompliance framework filter, e.g. SOC 2, ISO 27001, HIPAA
pricing_modelNoPricing model filter, e.g. annual-contract, usage, quote

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Agent category slug (compliance, security, risk, privacy, business-ops, code-security, or security-catalog slugs agent-identity, agent-governance, agent-runtime-security, agent-secrets)"New value: +"Agent category slug (compliance, security, risk, privacy, business-ops, code-security, or security-catalog slugs agent-identity, agent-governance, agent-runtime-security, agent-secrets, guardrails-prompt-injection, mcp-gateways-scanners, ai-red-teaming)"
  2. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Agent category slug (compliance, security, risk, privacy, business-ops, code-security)"New value: +"Agent category slug (compliance, security, risk, privacy, business-ops, code-security, or security-catalog slugs agent-identity, agent-governance, agent-runtime-security, agent-secrets)"
    • addedInput schema / properties / segment
      Added value: +{
      +  "description": "Catalog segment. Omit for the main GRC directory. \"agent-security\" for tools that secure or govern AI agents. \"all\" searches both. Default excludes the security catalog.",
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so safety is covered. The description adds real value beyond that: the default response excludes the security catalog, results come with canonical theagentindex.io URLs, and it explicitly states it is not a ranking — a useful expectation-setting detail about ordering.

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?

It is short and front-loads the trigger condition before the segment mechanics. The clipped fragments ("Canonical theagentindex.io URLs. Not a ranking.") are efficient but slightly telegraphic rather than fully formed guidance.

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 six optional params and no output schema, the description covers the key decision — which catalog segment is searched — and sketches the return shape (main directory plus a separate named group). It omits result-count/pagination behavior tied to limit and how filters combine, which are minor residual gaps.

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 83%, so the schema already documents limit, query, segment, category, framework and pricing_model. The description reinforces the segment default behavior but adds nothing about limit, pricing_model, or how query interacts with category/framework filters, so it sits at the baseline.

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?

The description names a concrete verb+resource (search agents/tools) and bounds the domain to compliance, GRC and security catalogs, plus the segment scope. It is clear enough to distinguish from get_agent or compare_agents by implication, but it never names a sibling or states the boundary 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?

"Use when the user asks for AI agents or tools for a compliance, GRC or security task, or by framework" gives a clear triggering condition, and the segment instructions (agent-security for that catalog only, all for both) tell the agent how to widen scope. No when-not-to-use or named alternative is given, so it falls short of a 5.

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.