Skip to main content
Glama
jasonwilbur

oci-pricing-mcp

by jasonwilbur

calculate_networking_cost

Read-onlyIdempotent

Calculate the cost of OCI networking resources, including load balancers, bandwidth, FastConnect, VPN, and NAT gateways, with free tier credits applied.

Instructions

Calculate networking cost for a specific configuration, including free tier credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flexibleLoadBalancersNo
loadBalancerBandwidthMbpsNo
networkLoadBalancersNo
outboundDataGBNo
fastConnectGbpsNo
vpnConnectionsNo
natGatewaysNo
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the tool is safe and idempotent. The description adds that it includes free tier credits, which is useful context but minimal.

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?

The description is a single concise sentence with no wasted words. However, it could be expanded slightly to include more useful information without becoming verbose.

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

Completeness2/5

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

With 7 parameters and no output schema, the description is too minimal. It does not explain what the output looks like, how free tier credits affect the calculation, or what the parameters represent in detail. For a tool with many siblings, more context is needed for correct invocation.

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?

The input schema has 7 parameters with 0% description coverage. The description does not explain any parameter meanings, units, or constraints. While parameter names like 'fastConnectGbps' are somewhat self-explanatory, the lack of any description is a significant gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool calculates networking cost for a specific configuration and mentions free tier credits. This distinguishes it from sibling tools like calculate_database_cost or calculate_storage_cost.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jasonwilbur/oci-pricing-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server