Skip to main content
Glama

NS Pros MCP Gateway

aws-mcp__aws___search_documentation

AWS docs search. Each result's context is verbatim page text -- a real chunk of the actual page, not a short snippet -- and usually already contains the answer, so answer directly from it. Use read_documentation only when the chunks genuinely lack the needed detail.

Pick ONE topic. Add a 2nd ONLY if query genuinely spans domains. Extra topics dilute ranking.

  • reference_documentation -- API/SDK/CLI specs, config params

  • current_awareness -- new/released/announced

  • troubleshooting -- erro

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": {
      "search_phrase": "<search_phrase>"
    },
    "name": "aws-mcp__aws___search_documentation"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default 4).
topicsNoUp to 3 from: reference_documentation, current_awareness, troubleshooting, amplify_docs, cdk_docs, cdk_constructs, cloudformation, agent_skills, strands_docs, general. Default ["general"].
search_phraseYesKeywords; preserve exact error strings and all task terms verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the shape and quality of results ("verbatim page text... usually already contains the answer"), which tells the agent to answer directly rather than chain calls. It also discloses a ranking sensitivity (extra topics dilute results). It does not mention rate limits, auth, or result ordering, which keeps it short of a 5.

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?

Front-loaded with the highest-value fact (results usually contain the answer) followed by the routing rule and a scannable bullet list. The ending is truncated ("troubleshooting -- erro"), which leaves an incomplete list and slightly weakens the finish, but there is little wasted prose otherwise.

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 three-parameter search tool with no output schema, the description covers what the tool returns, how to consume it, when to escalate to read_documentation, and how topics affect ranking. The truncated topic legend is the main gap; pagination/limit behavior is already handled by the schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description exceeds it by explaining topic-selection strategy and the ranking cost of over-specifying topics. It partially annotates topic meanings (reference_documentation, current_awareness, troubleshooting), though the trailing list is cut off mid-word and 7 of the 10 schema-listed topics are left unexplained.

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?

"AWS docs search" gives a specific verb and resource, and the description immediately clarifies the nature of the returned data (verbatim page chunks, not snippets). It explicitly names the sibling it is not ("Use `read_documentation` only when the chunks genuinely lack the needed detail"), so an agent can route between the two without inspecting schemas.

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?

Provides concrete when-to-use and when-not-to-use rules: search first, read_documentation only as fallback. It also gives a scoping heuristic for topics ("Pick ONE topic. Add a 2nd ONLY if query genuinely spans domains") with the stated reason that extras dilute ranking, plus a topic taxonomy to choose from.

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.