Skip to main content
Glama

Custom Solutions

Get digital services

get_services
Read-onlyIdempotent

The nine parts of the Custom Solutions digital-services offer (private AI knowledge system, AEO, MCP server, managed websites), with short and long descriptions. Prices are not published; pricing is quoted per engagement.

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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context beyond them: the result set contains nine entries with both short and long descriptions, and the 'prices are not published; pricing is quoted per engagement' line preempts an agent from asking for a price or fabricating one.

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?

Two sentences, front-loaded with the resource and its scope, followed by the pricing caveat. Slight density from the parenthetical examples, but no sentence is filler.

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 parameters, no output schema and safety covered by annotations, the description carries the remaining burden well: it says what the tool returns (nine parts, short and long descriptions) and the one policy boundary an agent would otherwise get wrong (no published pricing). Only an explicit usage trigger is missing.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies no filtering arguments are needed.

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?

States a specific verb and resource (the nine parts of the Custom Solutions digital-services offer) and enumerates representative entries plus the return shape (short and long descriptions). It is clearly a catalog-lookup tool, distinguishable from the compute_* siblings, though it doesn't explicitly name a sibling to defer to.

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 infers it should call this when it needs an overview of offered services. There is no explicit when-to-use/when-not statement, no mention of prerequisites, and no pointer to an alternative for deeper detail.

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