Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

A finding's drafts

webops_drafts
Read-onlyIdempotent

One finding's drafted fixes and their change requests. A finding of another organization answers not found. It changes nothing.

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": {
      "finding_id": "<finding_id>"
    },
    "name": "webops_drafts"
  }
}

Input Schema

NameRequiredDescriptionDefault
finding_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

B3.4/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 the bar is lower. The description adds one real behavioral fact: a cross-organization finding returns a not-found result. 'It changes nothing' simply restates readOnlyHint and therefore adds no new information. Nothing is said about how many drafts come back, ordering, or what a draft record contains.

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?

Three short sentences, front-loaded with what is returned. The closing sentence 'It changes nothing' is redundant with the readOnly annotation and earns no place, but the definition is otherwise tight and free of padding.

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?

The rich annotations mean the safety profile is covered, and the tool is a simple read with one parameter. However, there is no output schema, so the description is the only place to learn what a 'draft' or a 'change request' actually contains, and it says nothing about that. Adequate for calling the tool, thin for interpreting the response.

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?

There is one parameter, and its schema has no description at all (0% coverage), so the description carries the burden. 'One finding's drafted fixes' plus the cross-organization not-found rule together imply that finding_id must be a finding in the caller's organization, which is useful context. The description never names the parameter, states its format, or says where a valid id comes from, 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?

The description states that the tool returns one finding's drafted fixes plus their change requests, which is a concrete resource and scope. It also implicitly distinguishes itself from the plural `webops_findings` sibling by scoping to a single finding. It never names a verb such as 'list' or 'get', but the retrieval intent is unambiguous.

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: an agent infers it should call this when it needs the drafts belonging to a known finding. The description never explicitly says 'use when you have a finding_id' or names an alternative such as `webops_draft_fix` for a single draft or `webops_findings` for the finding list. One exclusion is supplied (findings from another organization), which is genuine 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