Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

Search workspace notes

connections_notes_search_company_notes
Read-only

Search this member's WORKSPACE notes by meaning (not keyword) and return the most relevant passages. Needs the workspace's company id; ask which company if the member has several. Only notes left visible to AI are searched; personal notes never.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many passages to return (default 8, maximum 25).
queryYesWhat to look for, as a question or topic.
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
projectNoWorkspace to run this call in (id or name).
companyIdYesThe workspace's company id, from the member's company list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / companyId / description
      Previous value: -"The id of the company/workspace whose notes to search - from the member's own company list."New value: +"The workspace's company id, from the member's company list."
    • addedInput schema / properties / person
      Added value: +{
+  "description": "Linked person to run this call as (first name). Omit to run as the connection's holder.",
+  "type": "string"
+}
    • changedInput schema / properties / query / description
      Previous value: -"What to look for, in plain language - a question or a topic, not keywords."New value: +"What to look for, as a question or topic."
  2. Changed1 schema field changed
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Workspace to run this call in (id or name).",
+  "type": "string"
+}
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly=true and destructive=false, and the description adds non-obvious behavior the annotations cannot convey: retrieval is semantic rather than keyword-based, and the searchable corpus is restricted to AI-visible notes with personal notes excluded. It does not discuss ranking, scoring, or what a passage looks like, but the annotations carry the safety profile.

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?

Three short sentences with the search mode and scope front-loaded, then the prerequisite, then the visibility constraint. Capitalized WORKSPACE and the parenthetical 'not keyword' carry emphasis without extra sentences, and nothing is redundant.

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 five-parameter search with full schema coverage and no output schema, the description covers the retrieval mode, the corpus restriction, and the prerequisite/disambiguation path. Nothing an agent needs in order to call it correctly is missing.

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, but the description adds genuine meaning for the central parameter by specifying that 'query' should be phrased conceptually rather than as a keyword string. It also reinforces that companyId is mandatory and ambiguous when the member has multiple companies, which shapes how the agent obtains the value.

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 names a specific verb and resource ('Search this member's WORKSPACE notes') and immediately qualifies the retrieval mode as semantic ('by meaning (not keyword)'). It also scopes the corpus ('Only notes left visible to AI are searched; personal notes never'), which implicitly separates it from the personal-notes sibling, though it never names that sibling.

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?

It states a hard prerequisite ('Needs the workspace's company id') and prescribes a disambiguation behavior ('ask which company if the member has several'), which is actionable guidance an agent can follow. It stops short of explicitly saying when to prefer this over connections_notes_search, leaving that inference to the personal-notes exclusion.

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

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