Skip to main content
Glama
Sign In

mcp

by com.makehybrid
OverviewDiscussionsAdmin

MakeHybrid API: The LinkedIn accounts this organization has connected, which are the only ones anything here may act as. Start here when a request names a person's account: an id that is not on this list answers 404 everywhere else.

complete_connect_accounts
Read-onlyIdempotent

The LinkedIn accounts this organization has connected, which are the only ones anything here may act as. Start here when a request names a person's account: an id that is not on this list answers 404 everywhere else. -- MakeHybrid API plan, GET /linkedin/connect/accounts, group connect.

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": "complete_connect_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional query-string parameters, e.g. {"limit":"20","cursor":"..."}. Values are coerced to strings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description's genuinely added value is the 404-on-unknown-id contract, which is useful but the only behavioral fact beyond the annotations; return shape and pagination are not described.

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?

The two substantive sentences are front-loaded with the key constraint first. The trailing '-- MakeHybrid API plan, GET /linkedin/connect/accounts, group connect' is boilerplate metadata that duplicates structured context and does not earn its place.

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?

With no output schema, the description does establish that the result is a list of account ids and that unknown ids fail elsewhere, which is enough for an agent to know what it is retrieving. It could say more about the fields returned per account, keeping it below 5.

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% and the single nested query object is fully described, so the schema carries the burden. The description adds nothing about the limit/cursor pagination parameters implied by the endpoint, so the baseline 3 applies.

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 resource (the organization's connected LinkedIn accounts) and a scope constraint ('the only ones anything here may act as'). An agent can distinguish it from LinkedIn search siblings, though it does not explicitly name those siblings as alternatives.

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?

'Start here when a request names a person's account' gives an explicit trigger condition, and the 404 note tells the agent what happens on a miss. No explicit when-not guidance or named alternative, so short of a 5.

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

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