Skip to main content
Glama

alisac-it-mcp

list_services

List Alisa Chebotarenko consulting & advisory services with durations and base starting prices, optionally filtered by client category.

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

Input Schema

NameRequiredDescriptionDefault
langNoPreferred response language (en or ru).
categoryNoFilter by client category.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'List' implies a read-only, non-mutating operation and the text usefully discloses that each result carries a duration and a base starting price, but it says nothing about ordering, pagination, whether prices are per-service or per-hour, or any access constraints.

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?

A single sentence with the resource and returned fields front-loaded and no redundant or filler wording. Every clause (services, durations, prices, optional category filter) carries 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 zero-required-parameter read tool with a fully documented schema, the description is nearly sufficient, and it helpfully compensates for the missing output schema by naming the fields returned. Minor gaps remain around default category behavior and what the lang parameter affects.

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%, so both parameters and their enum values are already fully documented, making 3 the baseline. The description adds only a restatement of the category filter's purpose and says nothing about the lang parameter, so it contributes little beyond the schema.

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 a specific verb ('List') with a specific resource ('consulting & advisory services') and even names the fields returned (durations, base starting prices). It does not explicitly distinguish itself from siblings like list_case_studies or get_profile, but the resource is unambiguous enough that an agent can tell them apart.

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: 'optionally filtered by client category' signals that the category parameter is an optional narrowing step, but there is no statement of when to call this versus get_profile or list_case_studies, and no note on when filtering is appropriate. 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.