Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Pin searches to follow

webops_set_ranking_pins
Destructive

Sets the searches pinned in one of the organization's websites' rankings, one per line, inside the plan's limit. 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>",
      "searches": "<searches>"
    },
    "name": "webops_set_ranking_pins"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
searchesYesOne search per line; the pinned set becomes exactly these.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the description's real contribution is the two-phase behavior: 'Nothing happens until the person confirms' and the return of a summary plus a code for tc_confirm. That is meaningful workflow context an agent cannot get from the annotations. It does not explain what happens when the plan limit is exceeded, and 'the pinned set becomes exactly these' sits slightly at odds with idempotentHint=false, though not enough to constitute a contradiction.

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?

Two compact sentences with no filler, and the most consequential fact (nothing is applied until confirmation) is stated plainly. The opening clause is slightly convoluted with stacked possessives ('one of the organization's websites' rankings'), but overall it is well sized.

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 two-parameter setter with no output schema, the description covers the essentials: what gets replaced, the plan limit, the confirm-code handoff, and that a summary is returned. Remaining gaps, such as error behavior on limit overflow or the shape of the summary, are comparatively minor.

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?

Schema coverage is 50%: the 'searches' field is already described, while 'domain' has no schema description. The description adds only modest value, clarifying that domain identifies 'one of the organization's websites' and that the input set replaces the existing pins, plus the 'one per line' framing that the schema already supplies.

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: it sets the pinned searches for one organization website's rankings, replacing the pinned set wholesale. That is clearly distinct from read-style siblings such as webops_searches, though the description never names a sibling to reinforce the contrast.

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?

Usage is only implied: the phrase 'inside the plan's limit' hints at a quota precondition, and the confirmation flow implies this is a staged write rather than an immediate one. There is no explicit statement of when to choose this over webops_searches or the other webops_set_* tools, and no when-not guidance.

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