Skip to main content
Glama
Sign In

Convocore

by app.convocore.mcp
OverviewDiscussionsAdmin

get_mcp_connection

Read-onlyIdempotent

Sign-in status of one MCP server connection and the agents that use it. Use it after the user finished a connect link. needs_reauth means the sign-in expired or was revoked: create_mcp_connect_link with this connectionId.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "connectionId": "<connectionId>"
    },
    "name": "get_mcp_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, so the description is free to add domain behavior — the needs_reauth state meaning (expired/revoked) and the follow-up action. It stops short of describing behavior for an unknown or deleted connectionId.

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, front-loaded with what is returned, then the trigger, then the exception handling. Every sentence earns its place with no repetition of annotations or 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?

With no output schema, the description does explain the meaningful return content (sign-in status, associated agents, needs_reauth flag). The remaining gap is field-level shape of the response, which an agent may still need to infer.

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?

One required parameter with 0% schema description coverage, so the description must carry the load; it only references 'this connectionId' in the remediation sentence without defining the identifier or where to obtain it. Enough to map the param to an MCP connection, not enough to source it confidently.

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 concrete resource and scope: sign-in status of ONE MCP server connection plus the agents that use it. This cleanly separates it from list_mcp_connections (plural) without naming it, though an explicit contrast with the listing sibling would have earned a 5.

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?

Gives an explicit trigger ('after the user finished a connect link') and a remediation branch pointing to create_mcp_connect_link when needs_reauth appears. No explicit when-not-to-use condition, but the lifecycle placement is clear.

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

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