Skip to main content
Glama

Coline

Search mentions

search_mentions
Read-onlyIdempotent

Finds Coline items the person can @-mention by name: people, channels and direct messages, docs, notes, files and tasks, in their default workspace unless one is named. Use it to resolve an @-mention to a Coline id and link.

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_mentions"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindsNoOnly these kinds.
limitNo
queryYesWhat the person typed after @; may be empty.
workspaceNoWorkspace slug; default: the person's default workspace.

Output Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world behavior, so the bar is lower. The description still adds real context: results are limited to items the person can actually mention (permission-scoped) and default to the caller's default workspace unless one is named, which is behavior an agent would otherwise have to guess.

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: the first defines the resource set and workspace scoping, the second states the intended use. The most decision-relevant information (what is searchable) is front-loaded.

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?

Return values are covered by the output schema, and the description covers scope, default workspace, and the resolution-to-id purpose. For a 4-parameter read tool this is nearly complete; only edge cases such as empty-query behavior or result ordering are unaddressed.

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 coverage is 75%, so most parameters are already documented. The description reinforces the query meaning ('what the person typed after @', resolvable to an id) and restates the workspace default, but adds little beyond the schema for 'kinds' and 'limit'.

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?

The description uses a specific verb ('Finds') and enumerates the exact resource types it covers (people, channels, DMs, docs, notes, files, tasks) plus the ability scoping ('the person can @-mention'). It is clearly distinguishable from generic 'search' siblings, though it does not name any specific sibling to contrast with.

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?

'Use it to resolve an @-mention to a Coline id and link' states the concrete task this tool serves, giving a clear trigger context. It lacks explicit exclusions or a named alternative (e.g., when to prefer a general search tool), so it stops short of full when/when-not guidance.

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