Skip to main content
Glama

Get customer reviews summary

get_reviews_summary
Read-onlyIdempotent

Customer rating summary: Google rating and review count and Thumbtack rating, each with the date it was checked. Use when asked about reputation. Counts change over time; the date shows how fresh they are.

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_reviews_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new context beyond that: counts change over time and the embedded date signals freshness, which warns the agent the values may be stale. It says nothing about caching, refresh cadence, or what happens when a platform has no listing, so it is useful but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with what is returned and followed by the usage trigger and the freshness caveat. Every clause earns its place and nothing is repeated from the annotations or title.

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-parameter read with full annotation coverage, the definition covers what is returned, when to call it, and the key caveat about changing counts. With no output schema, it does name the returned fields, though it does not state the response shape or what an unrated platform looks like — a minor gap for a tool this simple.

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, so there is no parameter meaning to explain and the baseline applies. The description cannot add parameter guidance because none is needed, and it correctly spends its words on the returned fields instead.

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 the exact resource and payload: Google rating, review count, Thumbtack rating, each with the date checked. That is far more specific than the title alone. It does not explicitly contrast with a sibling, but no sibling in the list covers review/reputation data, so the scope is self-evident.

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 asked about reputation" gives a concrete trigger condition that maps a user intent to this tool. It stops short of stating when not to use it or naming alternatives (for example, a general company-info or pricing tool for broader requests), so it is clear context without exclusions.

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