Skip to main content
Glama

Agent Index — GRC & Compliance

Get an agent listing

get_agent
Read-onlyIdempotent

Use when the user names a specific agent or product and wants its listing details. Returns that one listing, with the canonical page URL, summary, frameworks, tasks and source citations.

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": {
      "slug": "<slug>"
    },
    "name": "get_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesAgent slug, e.g. vanta

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral content by describing the returned record's fields, which matters because there is no output schema. It stops short of stating not-found/error behavior for a bad slug.

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 sentences, zero filler, with the usage condition front-loaded and the return contents second. Every clause earns its place.

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?

For a one-parameter, read-only lookup with full annotation coverage and no output schema, the description is nearly sufficient: it explains when to call it and what comes back. The remaining gap is failure-mode behavior when the slug does not resolve.

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 100% and the single slug parameter is already documented with an example, so the schema carries the weight. The description's phrase 'names a specific agent or product' hints that product names can map to a slug, but it adds no format, casing, or canonical-slug rules beyond the schema.

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 states a specific verb (returns one listing) and resource (agent/product listing), and enumerates the payload fields: canonical page URL, summary, frameworks, tasks, source citations. It implies a single-record lookup versus the sibling search_agents, but never names the alternative, so differentiation is left partly to inference.

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?

It gives a clear triggering condition: the user names a specific agent or product and wants its listing details. That is a usable when-to-use rule, but there is no explicit exclusion (e.g. 'do not use for discovery/browsing — use search_agents') and no guidance on what to do if the slug is unknown.

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.