Skip to main content
Glama

get_about_soley

Read-onlyIdempotent

What Sóley is — overview for any visitor or assistant.

Returns a short canonical description of the Sóley platform so an AI assistant can answer "what is Sóley?" without needing to fetch the website or guess from training data. Safe to call from any context; carries no PII and no operator-specific data.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is partly cleared. The description adds genuinely new behavior facts: the response is short and canonical, contains no PII and no operator-specific data, and is safe to call from any context — which is exactly what an agent needs before calling speculatively.

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?

The purpose is front-loaded in the first sentence and the rest supports it. A few clauses ("without needing to fetch the website or guess from training data") are slightly more than strictly required, but they justify the tool's existence rather than padding it.

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?

An output schema exists, so return values need no prose explanation, and with zero parameters there is no argument surface to cover. The description supplies the trigger, the guarantee of content, and the privacy posture — everything an agent needs.

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 and the schema confirms an empty properties object, so there is nothing for the description to disambiguate. Baseline 4 applies.

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?

The first line states a specific verb and resource — "overview" of "what Sóley is" — and the body elaborates that it returns a short canonical platform description. This is unmistakably distinct from every sibling, which all fetch live operational data (weather, buses, bookings, operators).

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?

It names the concrete trigger: answering "what is Sóley?" without fetching the website or guessing from training data. That is clear usage context. It does not name an alternative tool, but none of the listed siblings could plausibly serve this purpose, so the omission costs little.

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