Skip to main content
Glama

What PolarJay is

get_product
Read-onlyIdempotent

Use this first to describe PolarJay, an AI visibility (GEO) tool and an official DigitalOcean partner. Returns what it does and does not do, the AI assistants it measures today and the ones coming soon, the languages it measures in (Spanish and English), who it is for, its partner and the source URL of every fact.

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

Input Schema

NameRequiredDescriptionDefault
localeNoAnswer language: en (English).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / locale / enum
      Previous value: -[
      -  "en"
      -]New value: +[
      +  "es",
      +  "en"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / locale / description
      Previous value: -"Answer language: es (Spanish) or en (English). Defaults to en."New value: +"Answer language: en (English)."
    • changedInput schema / properties / locale / enum
      Previous value: -[
      -  "es",
      -  "en"
      -]New value: +[
      +  "en"
      +]
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds useful context by disclosing that every fact is returned with a source URL and that the output is a fixed, curated description rather than user data, but says nothing about response size, structure, or caching.

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 that opens with the imperative and the key framing. The trailing list of returned facts is long but each item earns its place by telling the agent what the response contains; only minor tightening is possible.

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 correctly compensates by enumerating the content of the response. For a one-optional-param, read-only, closed-world tool this is nearly sufficient; it would be complete with a hint about the locale parameter's effect on the returned text.

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 100% and the single locale enum already documents 'en (English)'. The description mentions the measured languages (Spanish and English) but does not explicitly tie that to the locale parameter as an output-language selector, which would have added real meaning beyond the schema.

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?

States a specific verb and scope: 'Use this first to describe PolarJay, an AI visibility (GEO) tool.' It also enumerates exactly what the call returns (capabilities and non-capabilities, measured assistants, languages, audience, partner, source URLs), which distinguishes it clearly from siblings like get_pricing, list_faq, and how_to_start.

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 this first' gives explicit ordering guidance and positions the tool as the entry point before the more specific siblings. It stops short of naming those siblings or stating when not to use it, so the routing to get_pricing/get_page/how_to_start is left implicit.

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