Skip to main content
Glama

Product facts

get_product_facts
Read-onlyIdempotent

Current facts about the CheaterBusting check: the dating apps each plan covers, plan prices and add-ons, delivery times and the late-report refund, what CheaterBusting never accesses, and the link where a person starts a check. Call it before answering questions about the check. Read-only; it cannot place orders or take payments.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description still adds concrete behavior by stating it cannot place orders or take payments and by marking the data as 'current'. What remains undisclosed is return shape and whether facts are scoped per locale, which the absent output schema leaves to inference.

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?

Three sentences, front-loaded with the fact inventory and followed by the invocation cue and the read-only caveat. Every clause carries distinct information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A no-parameter, read-only informational tool with no output schema: the description fully lists the content an agent will get back and warns off transactional use. Nothing needed to call it correctly is missing.

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?

Zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. No hidden input expectations are introduced by the text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb ('get') and an enumerated resource: dating apps each plan covers, plan prices and add-ons, delivery times and late-report refund, access boundaries, and the start-a-check link. An agent can tell this apart from get_page, list_blog_articles, or search_site purely from the content scope listed.

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?

'Call it before answering questions about the check' gives an explicit trigger condition, and the closing line rules out transactional uses. There is no named alternative or when-not-to-use case, but the narrow subject matter makes misuse unlikely.

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.