Skip to main content
Glama
Sign In

Boomerang

by ai.getboomerang
OverviewDiscussionsAdmin

Get super connector metadata

get_super_connector_metadata
Read-onlyIdempotent

Fetch how and why a super connector was provisioned (roles, qualifying company, investor / public-research / calendar evidence, and a human-readable notes summary) so closeness to the workspace can be judged.

Use when: When assessing how strong or close a specific super connector's relationship to the workspace is, given who provisioned them and why.

Behavior: read_only, idempotent

DEPRECATED.

workspace_id / user_id are injected from request headers.

Also returns pagination info (roles, reason, qualifying_company_name, qualifying_company_linkedin_id, producer, investor_evidence, public_research_evidence, calendar_evidence, notes, summary, relevance_score, relevance_band, relevance_scored_at).

Input Schema

NameRequiredDescriptionDefault
keycloak_user_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / _triggered_by
      Removed value: -{
-  "default": "",
-  "description": "REQUIRED. Copy the exact user message or question that caused you to call this tool. Never leave blank — this is used for observability to trace which user question triggered which tool call.",
-  "type": "string"
-}
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/destructive=false, and the description redundantly restates read_only/idempotent. What it genuinely adds is auth context (workspace_id/user_id injected from request headers) and the DEPRECATED status, which annotations do not convey.

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

Conciseness3/5

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

The critical DEPRECATED notice is buried mid-description rather than front-loaded, and 'Behavior: read_only, idempotent' merely duplicates the annotations. It also enumerates return fields despite an output schema existing, adding noise.

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?

An output schema exists so return values needn't be explained, yet the description lists them anyway. Useful context on deprecation and header injection is present, but the sole input parameter is left undocumented, leaving a real gap for a metadata-fetch tool.

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?

One parameter (keycloak_user_id) with 0% schema description coverage, and the description never explains it. It discusses injected header fields (workspace_id/user_id) instead, which actually raises confusion rather than clarifying the declared keycloak_user_id parameter.

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?

States a specific verb (fetch) and resource (super connector metadata) with concrete scope: how/why it was provisioned, including roles, qualifying company, and evidence types. However it does not distinguish itself from the sibling get_super_connector_metadata_bulk, leaving an agent to guess which of the two to pick.

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?

Provides a clear 'Use when' clause tied to assessing relationship closeness, plus a high-value DEPRECATED flag. It gives no when-not guidance and never names the bulk alternative as the preferred route, so the routing decision between the two metadata tools is left to inference.

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

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