Skip to main content
Glama

Contact Mini Split Reef

get_contact
Read-onlyIdempotent

How to reach Mini Split Reef: the email address to give the customer, the website, and how to order.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is fully covered. The description's added value is disclosing the returned content (email, website, ordering info), which matters because there is no output schema, but it says nothing about freshness, formatting, or fallback behavior when contact data is unavailable.

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 front-loaded sentence with no filler, listing the three pieces of information returned. The phrase 'how to order' is slightly ambiguous against the place_order sibling, costing a point, but nothing is wasted.

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?

With no output schema, the description carries the burden of describing return values and does so at a high level (email, website, ordering instructions). For a zero-parameter read-only lookup this is nearly sufficient; only the exact shape and any missing-field behavior are left unstated.

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 nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly implies no inputs are needed to retrieve the contact block.

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 resource (contact details for Mini Split Reef) and enumerates the specific content returned: email address, website, and ordering instructions. It is clear what the tool provides, though it never states an explicit verb and does not distinguish itself from siblings like get_service_details or place_order, which the 'how to order' phrase brushes against.

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?

Usage is only implied: 'the email address to give the customer' hints that this is the tool to call when a customer needs contact or ordering information. There is no explicit when-to-use statement, no exclusion of alternatives such as place_order (which actually places an order rather than describing how), and no prerequisites.

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