Skip to main content
Glama

TraceVero

Inspect connection options

get_connection_options
Read-onlyIdempotent

Inspect separate local and remote paths, declared secrets, documented authentication and verification limits for a public entry.

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": {
      "id": "<id>"
    },
    "name": "get_connection_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
localeNoen

Output Schema

NameRequiredDescriptionDefault
idYes
connectionsYes
rule_versionYes
catalog_versionYes
dataset_versionYes
connection_rule_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuine context beyond that: it reports "declared" secrets and "documented" limits, implying it surfaces metadata rather than revealing secret values or actually performing verification. It still doesn't say whether the output is cached-live or what happens for a nonexistent entry.

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?

A single front-loaded sentence with the verb first and the enumerated contents following; no filler. It is dense enough that the list of four returned items reads as a packed phrase, but nothing is wasted.

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-value explanation is not strictly required, and the read-only annotations cover safety. However, for a tool with a patterned required identifier and a locale switch, the description omits both which entry ids are valid and what locale affects, leaving gaps an agent must infer.

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?

Schema description coverage is 0%, so the description carries the burden, yet it never mentions either parameter. The namespaced id pattern (mcp/..., agenten/...) and the de/en locale default are left entirely unexplained, with only the vague phrase "for a public entry" hinting at what id refers to.

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 ("Inspect") and enumerates the concrete resources exposed: local and remote paths, declared secrets, authentication and verification limits, scoped to "a public entry." An agent can tell this is a read-only introspection of connection metadata rather than an actual connect/fetch. It does not explicitly contrast itself with siblings such as configure or validate_config, so it stops short of 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage signal is the implicit scope "for a public entry"; there is no statement of when to call this versus configure, fetch, compare, or validate_config. Nothing tells the agent what precondition (e.g. having an entry id from search) is required before invoking it.

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