Skip to main content
Glama

Quote network product renewal

quote_network_product_renewal

Quote the next paid month for an owned network product at no charge, returning a quote and idempotency key to reuse for the paid renewal.

Instructions

Quote one next paid month for a network product; no charge. Preserve the returned quote and this idempotency key for renewal. Requires explicit networking:read for reads or networking:manage for changes; full/read defaults do not grant networking. The backend enforces ownership, feature availability and service 2FA locks. Read current capabilities and owned resource state first; obtain approval for the exact change. An accepted operation is pending, not proof of connectivity. Poll the returned operation/resource on its in_progress flag, waiting next_check_seconds between reads: while in_progress is true its reason_code is what is awaited (reason_kind waiting, e.g. a queued or pending reason, or a control plane that has not answered yet), never an error; only in_progress false with reason_kind failure is a failure. Preserve reason_code. On transport uncertainty inspect state and reuse only the original key and unchanged request; never automatically retry. Requires full API access, networking:manage, enabled paid operations, networking:order and spend caps. Choose a supported live catalog tier and its documented request kind; preserve the exact quote; disclose its gross_amount in EUR before user approval. The same Idempotency-Key is required for quote and confirmation. API-key checkout supports the advertised account-balance payment method only. Payment acceptance is not resource readiness.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
network_idYesExact lowercase UUID returned by an owned networking resource
resource_idYesExact lowercase UUID returned by an owned networking resource
idempotencyKeyYesStable Idempotency-Key for this exact intent; reuse unchanged on recovery, never generate a new key for an uncertain result

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.16

TDQS

A4.2/5.0
Behavior5/5

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

The description adds rich behavior beyond the annotations: permission requirements, ownership and 2FA enforcement, pending-operation semantics, polling and reason_code handling, transport-uncertainty recovery, spend caps, and payment-method limitations. These details are consistent with the annotations and greatly reduce ambiguity for an agent.

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?

The description is front-loaded with the core purpose and is information-dense, but it is very long and contains repeated permission and preservation instructions. It would benefit from clearer structure or bullets despite covering important complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's operational complexity, the annotations carry only basic safety hints, and there is no output schema, the description is complete enough. It explains the quote lifecycle, required permissions, polling behavior, failure semantics, approval requirements, and payment constraints.

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?

Schema coverage is already 100%, so the baseline is 3. The description adds meaningful semantics for idempotencyKey by requiring the same key for quote and confirmation, preserving it for renewal, and forbidding automatic retries with a new key.

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 a specific verb, resource, and scope: 'Quote one next paid month for a network product; no charge.' It makes the renewal-quote purpose clear, but it does not explicitly contrast this tool with close siblings such as quote_network_product or renew_network_product.

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?

It gives substantial when-to-use context, prerequisites, approval requirements, and catalog selection guidance. However, it does not explicitly name alternative sibling tools or state when this quote tool should not be used.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools