Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

Browse deals

connections_deals_list
Read-only

Use this when the member asks about Deals, deals, listings, what is for sale, raises, or their own postings. Returns rows from the public marketplace feed (scope 'feed', the default - always active, public listings) or the member's own listings across every status, including drafts (scope 'mine'). Filter by category, region or a free-text query; the feed also ranks a query by relevance. Each row carries its title, summary, category, region, capital sought, status and a link. To post a new deal, use connections_deal_create.

Input Schema

NameRequiredDescriptionDefault
limitNoMax deals to return (1-60, default 20).
queryNoOptional free-text search over the title, summary and description.
scopeNofeed (default) = the public marketplace. mine = only the member's own listings, every status included.
detailNocompact (default) = the fields needed to answer most questions. full = every field the deal carries.
fieldsNoOptional explicit field projection over each row; wins over `detail` when given.
offsetNoPagination offset, default 0.
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
regionNoOptional exact-match region or city filter.
statusNoOptional status filter. The public feed only ever holds 'active' listings - drafts and closed deals only ever show under scope 'mine'.
projectNoWorkspace to run this call in (id or name).
categoryNoOptional exact-match category filter, e.g. 'real-estate', 'saas', 'services'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Workspace to run this call in (id or name).",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[]
  4. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the description only needs to add scope behavior — and it does: the feed is always active public listings, 'mine' spans every status including drafts, and the feed ranks free-text queries by relevance. It stops short of describing pagination limits or ordering of results outside of relevance ranking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Front-loaded with the use-when clause, then scope behavior, then filters, then row contents, then the sibling pointer — a sensible order with little filler. The one sentence listing row fields is slightly listy but earns its place since there is no output 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?

For an 11-parameter read tool with no output schema, the description covers the selection criteria (which scope, which filters) and summarises the returned row shape (title, summary, category, region, capital sought, status, link). It leaves pagination and result ordering implicit, a minor gap given the fully documented schema.

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 100%, so the schema already documents limit, offset, detail, fields, person, project, status and the enums. The description reinforces the scope default and the category/region/query filters but adds no syntax or precedence detail (e.g. how 'fields' overrides 'detail') beyond what the schema states, so baseline 3 applies.

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 (browse/list) and resource (deals/listings) and immediately names the two scopes it can return, so an agent can tell it apart from connections_deal_create or connections_deal_update without opening a 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?

Opens with an explicit trigger ('when the member asks about Deals... raises, or their own postings') and names the alternative for the adjacent task ('To post a new deal, use connections_deal_create'). It also spells out which scope to pick for public vs. own listings, which is the main routing decision.

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