Skip to main content
Glama

Check Edworking connection

get_connection
Read-onlyIdempotent

Check the current connection name, granted permissions, and expiry. Does not return credentials or other connections.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
nameYes
scopesYes
expiresAtYes

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 already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's added value is what the annotations cannot say: the returned fields and the explicit exclusion of credentials and other connections. That negative disclosure is genuinely useful for an agent deciding whether this call is safe and sufficient. It does not discuss freshness/caching or what happens if no connection exists, which keeps it below 5.

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?

Two short sentences with no filler. The positive scope is front-loaded and the exclusion clause follows immediately where it is most useful.

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 parameters, rich annotations, and an output schema, the description only needs to frame purpose and result shape, which it does. The one small gap is that "connection" is not defined (auth session vs. integration bind), though the surrounding product context makes it inferable.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline is 4. The description correctly spends no words on input syntax and instead uses the space to describe the result.

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?

"Check the current connection name, granted permissions, and expiry" gives a specific verb and resource and enumerates the three things returned. The negative clause ("Does not return credentials or other connections") also separates it from the list_*/get_* siblings that surface other resources. It stops short of naming any alternative tool outright, so it is clear rather than fully differentiated.

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?

The intent (verify the active connection, its permissions, and its expiry) is implied by the field list, so an agent can infer this is a pre-flight/verification call. There is no explicit statement of when to call it, when not to, or which sibling to use instead. Adequate but leaves the routing decision to inference.

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.