Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Look up one search's results now

webops_look_up_search
Destructive

Looks up Google's results for one of the website's own searches now, spending one of the month's lookups (money); refused without room or within the reuse days of the last lookup. The result arrives with the next refresh. Nothing happens until the person confirms: this returns a summary and a code for tc_confirm.

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": {
      "domain": "<domain>",
      "query": "<query>"
    },
    "name": "webops_look_up_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesOne of the site's own Search Console searches (last 90 days).
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: quota consumption ('spending one of the month's lookups'), refusal conditions, deferred result delivery ('arrives with the next refresh'), and a mandatory confirmation step returning a tc_confirm code. This is consistent with destructiveHint=true and readOnlyHint=false. It doesn't state what a refusal response looks like or whether a refused call still costs a lookup.

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?

Dense and front-loaded: cost, eligibility, delivery timing, and the confirmation requirement each get one clause with little waste. The parenthetical '(money)' and run-on refusal clause are slightly awkward but still carry real information.

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?

For a mutating, quota-consuming, asynchronous tool, the description covers cost, eligibility, delivery timing, and the confirm handshake, which is close to what an agent needs. The missing piece is which tool completes the confirmation and how the domain parameter scopes the lookup.

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?

With schema coverage at 50%, the schema documents 'query' well but leaves 'domain' undocumented. The description only hints at site scoping ('the website's own searches') without explaining the domain parameter or its accepted format, so it only partially compensates for the coverage gap.

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 and resource ('looks up Google's results for one of the website's own searches now') and its scope ('one search'), which separates it from a bulk results fetch. It doesn't explicitly name sibling tools like webops_search_results or webops_refresh_now, so differentiation relies on inference from the 'now' vs 'next refresh' wording.

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 clear when-not conditions: refused without room in the month's lookups or within the reuse days of the last lookup, and explains that confirmation is required first. It lacks explicit routing to an alternative when the lookup is refused or when cached results would suffice.

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