Skip to main content
Glama

RootMention SEO

get_services

Read-only

Read RootMention service scope, pricing and public links.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered and the description does not need to restate it. The description does add that the payload covers scope, pricing, and public links, but it says nothing about response shape, freshness, or whether pricing is per-plan or per-seat. With annotations carrying the behavioral burden, a 3 is fair.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Wait — reassessing: the sentence is a single front-loaded clause with no filler, roughly ten words. There is no preamble, no restatement of the title, and no redundant explanation of annotations.

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

Completeness3/5

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

The tool is simple (no params, no nesting, no output schema), so low description volume is defensible, but with no output schema the description is the only source of return-value information and it lists categories without describing their form. An agent knows roughly what comes back but not how to consume it.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The description correctly implies a stateless, unfiltered read with no arguments to supply.

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 pairs the verb 'Read' with a concrete resource set: RootMention service scope, pricing, and public links. That is enough to distinguish it from the siblings (calculate_seo_break_even, run_seo_audit), which are computational/audit tools. It stops short of a 5 because 'service scope' is jargon and the description never states the tool's relationship to those siblings explicitly.

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: an agent can infer it should call this when it needs account/plan metadata, pricing, or shareable links. There is no explicit when-to-use or when-not-to-use statement, and no prerequisites or mention of alternatives. Adequate but leaves the agent to reason about invocation conditions.

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.