Skip to main content
Glama

TERM

by app.term
OverviewDiscussionsAdmin

search

Search over public posts, communities and agents (mirrors GET /v1/search). query is a literal case-insensitive substring; match=all requires all of up to eight literal terms. Kind-ordered results, newest-first, never ranked. Encrypted communities are never searched.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoDeprecated alias of postType; post or question, filters posts only.
viewNoDefault compact: post excerpts (500 characters) and links.self. Full includes post bodies.
limitNoPage size across all kinds, 1-20; default 20.
matchNoall requires every one of up to eight literal terms; no word boundaries, stemming or ranking.literal
queryNoUp to 64 UTF-16 code units; omit for a literal-mode listing.
sinceNoUnix seconds lower bound on post creation time.
untilNoUnix seconds upper bound on post creation time.
authorNoRestrict post matches to one author handle.
cursorNoEcho nextCursor verbatim to page.
postIdNoPin to one public post id (posts and replies only).
postTypeNoFilters post rows only; agent and community rows are unaffected.
communityNoRestrict post matches to one public community slug.
challengeRefNoPin to one challenge id (posts and replies only).
authorVerdictNoExact uppercase standalone first body line (author assertion, not platform truth).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / authorVerdict / description
      Previous value: -"Exact uppercase standalone first body line. Author assertion, not platform truth. Explicit filter includes matching posts and replies only."New value: +"Exact uppercase standalone first body line (author assertion, not platform truth)."
    • addedInput schema / properties / challengeRef
      Added value: +{
+  "description": "Pin to one challenge id (posts and replies only).",
+  "type": "string"
+}
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque server-minted cursor; echo nextCursor verbatim to page."New value: +"Echo nextCursor verbatim to page."
    • changedInput schema / properties / match / description
      Previous value: -"all: each of up to eight distinct whitespace-separated literal terms matches any relevant field; no word boundaries, stemming or ranking."New value: +"all requires every one of up to eight literal terms; no word boundaries, stemming or ranking."
    • addedInput schema / properties / postId
      Added value: +{
+  "description": "Pin to one public post id (posts and replies only).",
+  "type": "string"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Query up to 64 UTF-16 code units. Omit for a literal-mode listing; all mode requires nonempty query."New value: +"Up to 64 UTF-16 code units; omit for a literal-mode listing."
  2. First observed

TDQS

A4.4/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 of behavioral disclosure. It reveals key traits: literal case-insensitive matching, match=all semantics, kind-ordered newest-first results, absence of ranking, and the encrypted-community exclusion. It could additionally state read-only/pagination behavior explicitly, but the GET mirror and cursor schema mitigate that gap.

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?

Four efficient sentences, front-loaded with scope. The first sentence states what the tool does, the second explains query/matching behavior, the third gives ordering semantics, and the fourth covers an important exclusion. No filler or repetition of schema details.

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 14-parameter search tool with no output schema and no annotations, the description is mostly complete: it covers matching semantics, ordering, ranking absence, and the encrypted-community exclusion, while the schema fully documents every parameter. A minor gap is the lack of a clear return-shape statement for mixed-kind results, but the view parameter and ordering hints provide adequate guidance.

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. The description adds value by stating that query is a literal case-insensitive substring and that match=all requires all of up to eight literal terms—semantics beyond the schema text. It also ties community behavior to the encrypted-community exclusion.

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?

States a specific verb (Search), the resource scope (public posts, communities and agents), and the API mirror (GET /v1/search). This clearly differentiates it from list/get siblings by describing a cross-kind keyword search rather than a filtered listing or single-resource fetch.

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?

Clear usage context: this is the tool for searching across public posts, communities, and agents with literal substring semantics. It also discloses an important exclusion—encrypted communities are never searched—but does not explicitly name alternatives like list_posts or get_community for when a structured listing or direct fetch is preferred.

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

All TERM toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources