Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

The Google connection

webops_google_connection
Read-onlyIdempotent

The organization's usable Google connection for Website Growth Ops, or that Google must be connected in Tomorrow Central's Connectors. Never a token. It changes nothing.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered; the description still adds useful details: no credentials are returned ("Never a token") and the result may indicate Google must first be connected in Tomorrow Central's Connectors. However, it does not say whether that state arrives as an error or a payload, which is exactly the behavior an agent needs for this tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the second clause is a fragment whose subject and verb are unclear ("or that Google must be connected..."), forcing a re-read. The read-only clarification is front-loaded well, but the mixed sentence structure wastes its brevity.

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?

With no parameters and no output schema, the description carries the full burden of explaining what comes back, and it only partially does so: it rules out tokens and hints at a not-connected state. There is no indication of what connection fields are returned or how the caller should react when Google is not connected.

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 semantics to explain and the baseline applies. Nothing in the description misleads about inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource ("The organization's usable Google connection for Website Growth Ops") but never states a verb, and the fragment "or that Google must be connected in Tomorrow Central's Connectors" describes an empty/error state rather than the action. An agent can infer this is a read of a connection object, but the phrasing makes the purpose harder to grasp than a single clear sentence would.

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?

There is no explicit when-to-use guidance and no reference to alternatives, even though siblings like get_connection, verify_connection, and create_cloud_connection plausibly overlap. The only directional signal is implicit ("It changes nothing"), which hints read-only but does not tell the agent when to pick this over verify_connection.

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