Skip to main content
Glama

Coline

Search Coline

search
Read-onlyIdempotent

Use this to find docs, notes, files, tasks, messages and mail in a workspace by keywords. Returns titles, snippets and ids; pass an id to fetch for the full content. For events, use list_events.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
typesNoOnly these kinds of results.
cursorNonext_cursor from the previous page.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
resultsYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: it is a lightweight preview tool returning titles, snippets and ids, with full content deferred to fetch. It says nothing about result caps or paging, so it falls 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.

Conciseness5/5

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

Two sentences, no filler: scope first, then return shape, then the alternative for events. Every clause carries routing information and nothing is repeated from the schema.

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?

A broad multi-type search tool needs scope, return shape and sibling routing, all of which are present, and the output schema covers return fields. Pagination behavior via the cursor parameter is only implicit, which is the one small gap.

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?

With 60% schema description coverage, the schema already documents 'types', 'cursor' and 'workspace'. The description adds only that matching is by keyword for the query and that returned ids are fetch-ready, leaving 'limit' and the exact query matching semantics unexplained in prose.

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 states a specific verb ("find") and enumerates the exact resources covered (docs, notes, files, tasks, messages, mail) plus the mechanism (keywords, within a workspace). It also distinguishes itself from 'fetch' and 'list_events' by name, so an agent can route without opening another schema.

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 gives an explicit two-step workflow ("pass an id to fetch for the full content") and an explicit exclusion with a named alternative ("For events, use list_events"). This is when-to-use, when-not-to-use, and the alternative in one compact statement.

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