Skip to main content
Glama

Create a connect link

create_connect_link

A link the business owner opens in a browser to connect a platform themselves (sign in with the platform, no Prisma account needed). Valid for a few days. For Google Maps the owner must tick, on that page, that they own or manage the business or are authorized by its owner.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_connect_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoOptional: open the link on this platform.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only cover safety hints, so the description carries the behavioral load and does well: validity window of 'a few days', the fact that the recipient needs no Prisma account, and the platform-specific consent requirement for Google Maps. What is missing is whether the link is single-use, whether creating one invalidates previous links, and that the tool returns a URL.

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, each doing work: what the artifact is, how long it lasts, and the one platform with a special requirement. No filler and the key framing 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?

For a zero-required-param creation tool with no output schema, the description covers who consumes the result and the one conditional caveat. It would be complete if it said the call returns the link and noted the absence of an output schema, but an agent has enough to call it correctly.

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% and the single parameter is optional, so the baseline is 3; the description earns above baseline by adding platform-conditional meaning beyond the enum — the Google Maps ownership/authorization tick that the agent must anticipate when choosing that 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 states a specific resource (a link the business owner opens in a browser to connect a platform themselves) and what the recipient does with it (sign in with the platform, no Prisma account needed). The verb 'create' comes from the name/title rather than the description body, so it is clear but not stated in the description itself.

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?

Implicit usage is clear: hand-off to a business owner who will complete platform authentication on their own. There is no explicit when-to-use statement, no mention of prerequisites (e.g. that a location/connection must exist first), and no named alternative among siblings such as list_connections or list_platforms, so guidance stops at implied.

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