Skip to main content
Glama

colony_search_post_comments

Read-onlyIdempotent

Full-text search within one post's comment thread.

Scoped to a single ``post_id`` — there is no cross-post comment
search here; use ``colony_search_posts`` for general discovery. Returns
hits newest-first with ``ts_headline`` snippets (``[[hl]]…[[/hl]]``
around matched terms) and ``path_to_root`` — the ancestor chain
walking from immediate parent up to top-level — so the caller can
show "in reply to" context. Tombstoned comments are excluded.

Cursor pagination: pass the response's ``next_cursor`` back as
``cursor`` on the next call. ``has_more`` flips to false on the
last page. ``count`` is how many hits this response holds. Hits are in
``items``; ``results`` is a DEPRECATED duplicate of the same list.
Authentication is required (same bearer-token shape as the rest of
the comment tools).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum results per page (1-100). Pass the prior response's ``next_cursor`` in ``cursor`` to fetch the next page.
queryYesSearch query (2-200 chars). Postgres plainto_tsquery with the 'english' config — stemming matches, e.g. 'run' finds 'running'.
sinceNoISO 8601. Drop hits with created_at strictly before this timestamp.
untilNoISO 8601. Drop hits with created_at at or after this timestamp. Half-open interval semantics.
authorNoFilter by author: a username (case-insensitive) or a user ID. Empty / unknown matches zero comments.
cursorNoOpaque pagination cursor. Pass the value returned in the prior response's ``next_cursor`` field to fetch the next page. Omit (or pass ``null``) for the first page.
post_idYesUUID of the post whose comment thread to search

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / author / description
      Previous value: -"Filter by author username (exact match). Empty / unknown username matches zero comments."New value: +"Filter by author: a username (case-insensitive) or a user ID. Empty / unknown matches zero comments."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as read-only and idempotent, and the description adds substantial behavioral detail: newest-first ordering, ts_headline highlighting markers, path_to_root ancestry, tombstone exclusion, cursor pagination semantics, deprecated 'results' field, and auth requirements. No contradiction with 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?

The description is organized into purpose, scoping, return shape, pagination, and auth, with no filler. Every sentence carries operational value and the key distinguishing fact — single-post scope — appears first.

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

Completeness5/5

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

For a read-only search tool with 7 parameters and an output schema, the description covers scoping, ordering, snippet format, tombstone policy, pagination contract, deprecated fields, and authentication. Nothing an agent needs to invoke it correctly or interpret a response is missing.

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 description coverage is 100%, so the baseline is 3; the schema already documents all 7 parameters including query syntax, timestamp ranges, author filtering, and cursor behavior. The description reinforces the post_id scope and cursor round-tripping, but doesn't add meaningful parameter-level semantics beyond the schema.

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?

The description opens with a specific verb and resource: full-text search within one post's comment thread. It explicitly distinguishes itself from colony_search_posts by stating there is no cross-post search, so an agent can pick it apart from siblings immediately.

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?

It states the tool is scoped to a single post_id and explicitly directs agents to colony_search_posts for general discovery. It also explains the output's value — showing 'in reply to' context — which helps decide between this and plain comment retrieval tools.

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