Skip to main content
Glama

service_compare

Read-onlyIdempotent

Compare curated AWS service families against your constraints to evaluate trade-offs without automatic winners or fabricated scores.

Instructions

Compare curated AWS service families against user constraints. No automatic winner or fabricated scores.

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": {
      "family": "<family>"
    },
    "name": "service_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
familyYes
constraintsNo

Output Schema

NameRequiredDescriptionDefault
kindNo
optionsNo
sourcesNo
validatedNo
limitationNo
constraintsNo
decisionRequiredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedInput schema / required
      Previous value: -[
      -  "family",
      -  "constraints"
      -]New value: +[
      +  "family"
      +]
  2. First observedv0.4.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered elsewhere. The description adds a genuine behavioral disclosure, that it will not declare an automatic winner or invent scores, which shapes how an agent should interpret results. It says nothing about what 'curated' families contain or how results are ordered.

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?

Two short, front-loaded sentences with no filler; the comparison scope comes first and the output caveat second. Nothing is padded, though the brevity contributes to some of the specification gaps.

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?

An output schema exists, so return shape need not be described, and the enum covers valid families. Still, a comparison tool with two free-form-ish parameters leaves the agent guessing about constraint syntax and what distinguishes 'curated' families, which is thin for its complexity.

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 description coverage is 0%, so the description must carry parameter meaning; it does map 'family' to service families and 'constraints' to user constraints. However, it never explains what a constraint string should look like (free text? structured?), which matters given an array of up to 30 strings of 4000 chars. The family enum is self-documenting in the schema.

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 gives a specific verb and resource: 'Compare curated AWS service families against user constraints.' This tells an agent it is a decision-support comparison rather than a lookup or generator. It does not explicitly distinguish itself from the nearest sibling (service_equivalents), so it falls short of a 5.

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?

There is no statement of when to use this versus alternatives such as service_equivalents or aws_knowledge_search, and no prerequisites or exclusions. The only usage-adjacent signal is the caveat that no winner is produced, which describes output posture rather than tool selection.

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