Skip to main content
Glama

Stratalize Intelligence

Get Software Pricing Intelligence

get_software_pricing_intelligence
Read-only

Use when evaluating a new software purchase or reviewing a vendor quote for hidden costs. Returns common pricing models, hidden cost patterns, implementation cost ranges, and budget guidance by category. Example: CRM hidden costs — API overage $0.02/call adds $8,400/yr at 420K monthly calls, sandbox $1,200/mo additional, SSO integration $15K one-time — total cost 40% above list price. Source: Stratalize category pricing composite. $0.10 USDC per call.

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": {
      "category": "<category>"
    },
    "name": "get_software_pricing_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, openWorldHint, and destructiveHint, so the safety profile is covered. The description adds genuinely non-obvious behavior: the data source (Stratalize category pricing composite) and that each call costs $0.10 USDC, which matters for call budgeting. It does not discuss latency, caching, or what happens with an unrecognized category.

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?

Usage condition is front-loaded, then the return contents, then a worked example, then source and price. Every element is relevant, though the numeric example ($0.02/call, 420K calls, $8,400/yr) is heavier than needed to convey intent and pushes the pricing disclosure toward the end.

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 single-parameter, read-only lookup with no output schema, the description does the necessary work: it characterizes the returned payload, names the data source, and discloses per-call cost. The remaining gap is the valid-value space for 'category', which an agent needs in order to call it correctly the first time.

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 0% and the single required parameter 'category' is undocumented in the schema. The description compensates only partially: the phrase 'by category' plus the 'CRM hidden costs' example implies the parameter takes a software category like CRM, but it gives no list of valid values, no format guidance, and no statement about what happens for an unknown category.

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 uses a specific verb-and-resource framing: it returns pricing models, hidden cost patterns, implementation cost ranges, and budget guidance by category. That clearly separates it from generic sibling tools like get_saas_market_intelligence or get_vendor_contract_intelligence, though it never explicitly names or contrasts an alternative.

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 states a concrete triggering situation ('evaluating a new software purchase or reviewing a vendor quote for hidden costs'), which is enough for an agent to decide when to call it. It stops short of exclusions or naming the sibling tool to use when the question is about contracts or market sizing rather than pricing structure.

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