Skip to main content
Glama

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. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=true, openWorldHint=true, destructiveHint=false), the description discloses the data provenance ('Stratalize category pricing composite') and an explicit metered cost of '$0.10 USDC per call' — cost information an agent cannot get from structured fields. It also previews the shape of the return payload (pricing models, hidden cost patterns, implementation ranges, budget guidance) and illustrates it with a concrete worked example. It does not state freshness or coverage limits, so it falls short of 5.

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?

Structure is well front-loaded: trigger condition first, then returned content, then an illustrative example, then provenance and price. Every sentence serves a purpose. The CRM example is somewhat long relative to the rest, but it is the most informative part of the definition and earns its space.

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 supplies what an agent needs: when to call it, roughly what comes back, where the data comes from, and what it costs. The only material gap is valid values for 'category', which is left to inference from the example.

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 a single required parameter, 'category', with 0% schema description coverage and no enum, so the description carries the burden. It only partially compensates: the CRM example implicitly shows a plausible value ('category = CRM') and 'by category' signals the axis of segmentation, but no valid value set, casing, or granularity is specified. An agent can guess a value but has no way to confirm it is well-formed.

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 names a specific verb and resource: it 'returns common pricing models, hidden cost patterns, implementation cost ranges, and budget guidance by category.' That is far more concrete than a restatement of the name, and the domain (software purchase / vendor quote pricing) is distinguishable from the sibling intelligence tools. It stops short of explicitly contrasting itself with those siblings, which keeps it at 4.

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?

'Use when evaluating a new software purchase or reviewing a vendor quote for hidden costs' gives an explicit triggering situation rather than a vague hint. There is no when-not guidance or named alternative for adjacent questions (e.g. contract negotiation, which a sibling appears to cover), but the positive context is clear enough for an agent to select correctly.

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