Piping Toolset Engineering Data

Check the connection

verify_connector

Read-onlyIdempotent

Report whether the caller is signed in, the caller's tier, how many datasets return values at that tier, and the remaining daily lookups when the server tracks them. Returns no email, name or account id.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`tier`	Yes
`signed_in`	Yes
`caps_remaining`	Yes
`datasets_available`	Yes
`licensed_datasets_available`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.8/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, and closed-world behavior, so the description adds useful context by noting that no email, name, or account id is returned and that daily lookup counts appear only when the server tracks them. These are meaningful behavioral details beyond the annotation set, though credential or permission requirements are not discussed.

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?

The description is a single front-loaded sentence that lists each reported value without repetition or filler. Every clause contributes to understanding the tool's output scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter status tool with rich annotations and an output schema, the description is complete enough to understand what will be returned and the privacy boundary around the response. The missing usage routing is captured under usage guidelines rather than a gap in contextual completeness.

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 the baseline score is 4. The description adds no parameter semantics because none are available, and the empty schema fully covers the input contract.

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 verb ("Report") and a precise set of resources: sign-in state, caller tier, per-tier dataset coverage, and remaining daily lookups. This is clearly distinct from the dataset-oriented sibling tools, but the description does not explicitly differentiate itself from any named alternative.

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 description explains what the tool reports but gives no guidance on when to call it, when not to call it, or which alternatives exist for related checks. An agent must infer that this is the status/auth/quota endpoint from the title and description alone.

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

All Piping Toolset Engineering Data tools Inspect

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.