Skip to main content
Glama

How to start with PolarJay

how_to_start
Read-onlyIdempotent

The two ways to start: the free scanner (no sign-up) and the free trial (no card), with their URLs, plus the contact address.

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

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.6/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 covered. The description adds genuine content disclosure by enumerating what comes back (two sign-up paths, URLs, contact address), which is useful beyond the annotations. It does not describe the response shape or how the URLs are formatted, so it adds moderate rather than rich behavioral context.

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?

One compact sentence that front-loads the key fact (two ways to start) and then enumerates the payload elements. No filler, no restatement of the tool name, and nothing that could be cut without losing information.

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 simple, parameterless, read-only informational tool with no output schema, the description covers purpose and rough payload adequately. The remaining gap is that it never indicates the return format (prose vs. structured links), which matters slightly for a content-delivery tool. Given the low complexity and annotation coverage, this is close to complete.

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?

There is a single optional parameter, locale, with 100% schema description coverage and an enum of es/en, so the schema already carries the semantics. The description says nothing about language selection or that the answer language follows locale, leaving that entirely to the schema. Baseline 3 applies when the schema does the work.

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 concrete payload: the two onboarding paths (free scanner with no sign-up, free trial with no card), their URLs, and a contact address. That is more specific than the bare name 'how_to_start' and is clearly distinct from get_pricing, get_product, or list_faq. It stops short of explicitly contrasting itself with those siblings, so a 4 rather than a 5.

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?

Use is only implied: an agent can infer this is the tool for onboarding/"how do I begin" questions because the content is described. There is no explicit when-to-use statement, no exclusion such as 'for pricing use get_pricing', and no note on prerequisites. Adequate but leaves routing to inference.

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