Skip to main content
Glama

aws_knowledge_search

Read-onlyIdempotent

Search live official AWS documentation to answer architecture, configuration, and troubleshooting questions; queries go to AWS Knowledge, so omit secrets and customer data.

Instructions

Search live official AWS documentation. Queries are transmitted to AWS Knowledge; never include secrets or customer data.

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": {
      "query": "<query>"
    },
    "name": "aws_knowledge_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
topicNogeneral

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedInput schema / required
      Previous value: -[
      -  "query",
      -  "topic",
      -  "limit"
      -]New value: +[
      +  "query"
      +]
  2. First observedv0.4.1

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive, so safety is covered. The description adds genuinely new context: queries are transmitted to an external AWS Knowledge service and must not contain secrets or customer data, which is an important data-egress disclosure not present in 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the core purpose and followed by the safety constraint. Nothing is padded or redundant.

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

Completeness2/5

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

The privacy warning is valuable, but for a tool with three parameters, zero schema description coverage, and a ten-value topic enum that is undocumented everywhere, the description leaves an agent unable to use the tool's main filtering dimension correctly. It also omits any hint of result shape or result-count behavior, and there is no output schema to compensate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across all three parameters, so the description carries the full burden — yet it says nothing about the query length limits, the limit default/maximum of 5, or the ten-value topic enum (including obscure values like amplify_docs, cdk_docs, and agent_skills). An agent has no way to know which topic to choose without guessing.

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 uses a specific verb and resource — 'Search live official AWS documentation' — which tells an agent exactly what the tool returns. It does not explicitly contrast with the sibling aws_knowledge_read, so the search-vs-read distinction is only implied by the name.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no mention of when to prefer aws_knowledge_read or aws_regional_availability, and no advice on which topic value fits which situation. Usage is only inferable from the word 'Search'.

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