Skip to main content
Glama

Custom Solutions

Search answers and notes

search_answers
Read-onlyIdempotent

Full-text search over Custom Solutions' published answer pages and blog notes. Returns up to 10 matches with title, summary and canonical URL.

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": "search_answers"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPlain-language search, e.g. 'what is AEO'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a hard cap of 10 matches and the three returned fields (title, summary, canonical URL). It does not address result ordering, relevance ranking, or what happens with zero matches.

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 the scope first and the return contract second; every clause earns its place and nothing is filler.

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, no-output-schema search tool this is nearly complete: scope, result cap, and returned fields are all stated. Only minor gaps remain, such as how results are ordered and that a full page must be fetched via the related retrieval tool.

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?

There is a single parameter with 100% schema description coverage and a worked example already in the schema ('what is AEO'), so the schema carries the semantic load. The description's 'full-text search' framing adds modest context about how the query is matched but nothing the schema does not already provide.

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?

States a specific verb and resource ('Full-text search over Custom Solutions' published answer pages and blog notes') plus the result shape, which clearly separates it from the single-item get_answer sibling. It stops short of naming that sibling explicitly, so the differentiation is inferable rather than stated.

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

Usage Guidelines3/5

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

The phrase 'full-text search' plus 'published answer pages and blog notes' implies a discovery/lookup use case, but there is no explicit when-to-use framing, no exclusion (e.g. 'use get_answer to read a full page'), and no guidance on query formulation beyond the schema example.

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.

Resources