Skip to main content
Glama

Get free second opinion info

get_second_opinion_info
Read-onlyIdempotent

The free second-opinion service for homeowners who received an AC replacement quote from another company: what is covered, that it is free, and how to ask for it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_second_opinion_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. Beyond that, the description adds the eligibility precondition and the scope of the answer (coverage, the fact that it is free, and how to request it), which is real behavioral context; it stops short of describing delivery format or any limits.

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?

A single compact sentence with no filler, front-loading the subject and then listing the three things returned. The only weakness is that it is a noun-phrase fragment rather than a full statement of what the tool does.

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 zero-argument informational tool with rich annotations and no output schema, this covers the essential questions: who it serves and what the answer contains. A line on what the response looks like or how request steps are surfaced would close the remaining gap.

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?

The tool takes zero parameters and the description correctly implies no inputs are required, so there is nothing to mis-specify. The zero-parameter baseline applies.

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 resource — the free second-opinion service for homeowners holding a competitor's AC replacement quote — and enumerates the content it returns (coverage, cost, how to request). It is clearly distinguishable from siblings like get_pricing or estimate_replacement_cost, though it never states an explicit verb like 'returns' or 'explains'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The audience condition ('homeowners who received an AC replacement quote from another company') implies when this tool applies, which gives partial routing guidance. It does not explicitly say when not to call it or point to alternatives such as estimate_replacement_cost for homeowners who have no existing quote.

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