Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Questions asked of AI assistants

webops_ai_questions
Read-onlyIdempotent

The confirmed questions asked of AI assistants for a website, the plan's limit, and proposals from its own searches. Another organization's or an unconnected site answers not found. Read-only.

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>"
    },
    "name": "webops_ai_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

C2.7/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 safety is covered. The description adds genuine value by disclosing the response contents (questions, plan limit, proposals) and the negative case where another org's or unconnected site returns 'not found'. It does not say whether results are paginated, how many questions are returned, or what the plan limit means in the payload.

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?

Two short sentences with little waste, but the first crams three separate data categories into one clause and the second ('Another organization's or an unconnected site answers not found') is ungrammatical and slows comprehension. The key scoping information would read better front-loaded as an explicit imperative.

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?

For a single-parameter read tool with no output schema, the description covers purpose, the categories of returned data, and one failure mode. It leaves the parameter contract and the shape/magnitude of the response underspecified, which matters since no output schema exists to fill that gap.

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% for the single required 'domain' parameter, so the description must carry the load — but it only implies a website via 'for a website'. It never states whether domain takes a bare hostname, a URL, or a site ID, nor how it relates to the regex-constrained schema string.

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 — confirmed questions asked of AI assistants for a website, plus plan limit and proposals — but relies on a noun phrase rather than a verb (no 'list'/'get'/'retrieve'), so the operation is inferred, not stated. It separates itself from webops_set_ai_questions only indirectly via 'Read-only', and 'proposals from its own searches' is opaque to a first-time reader.

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 when-to-use or when-not-to-use guidance and no named alternative, even though a sibling named webops_set_ai_questions suggests a read/write pairing worth spelling out. The only conditional sentence concerns error behavior for other organizations or unconnected sites, which is not usage 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