Skip to main content
Glama
Sign In

Cobrain

by space.cobrain
OverviewDiscussionsAdmin

who_sees

Read-only

People who can see a note and can be @-mentioned in it, each with the Markdown to put in the note: writing [@Name](mention:<id>) notifies them (Cobrain's What's new, then an email). Mention only people the user asked you to notify.

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": {
      "path": "<path>"
    },
    "name": "who_sees"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
workspaceNoUsually omit; else brain id (as in search hits), 'mine', or owner name/email.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish that this is a safe read-only operation. The description adds meaningful behavioral context beyond the annotations: using the returned Markdown triggers notifications via Cobrain's What's new and then email, and users should only mention people they were asked to notify.

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 two sentences, front-loads what the tool returns, then explains the mention syntax and notification consequence. Every sentence adds useful information without repetition or filler.

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

Completeness3/5

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

It explains the returned content and the notification side effect of using the Markdown, which is important because there is no output schema. However, the required path parameter is left unexplained, leaving a noticeable gap for an agent trying to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The required path parameter has no description in the schema and is not explained in the tool description. The optional workspace parameter is described in the schema, but with only 50% schema coverage the description should compensate for the undocumented path parameter and does not.

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 clearly states the resource: people who can see a note and can be @-mentioned in it, each with Markdown mention syntax. It does not explicitly name or distinguish itself from siblings such as search_mentions, so it falls short of the sibling-differentiation bar for a 5.

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?

Usage is implied by the purpose: retrieve mentionable people when writing a note. The closing instruction 'Mention only people the user asked you to notify' adds a useful constraint, but there is no explicit when-to-use or when-not-to-use guidance versus alternatives like search_mentions.

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

All Cobrain 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