Skip to main content
Glama

recommendations_list

Read-onlyIdempotent

List automated recommendations for improving error monitoring setup, security and configuration, for a log or an organization (exactly one of logId or organizationId). Excludes description and suggestions; use recommendations_get_details for those.

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

Input Schema

NameRequiredDescriptionDefault
logIdNoThe ID (Guid) of the log to fetch recommendations for. Mutually exclusive with organizationId.
stateNoOnly recommendations with this state are returned.Open
organizationIdNoThe ID of the organization to fetch recommendations for. Mutually exclusive with logId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / logId / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • addedInput schema / properties / organizationId / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • addedInput schema / properties / state / enum
      Added value: +[
      +  "Open",
      +  "Ignored",
      +  "Fixed"
      +]
    • addedInput schema / properties / state / type
      Added value: +"string"
  2. Changed2 schema fields changed
    • removedInput schema / properties / logId / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
    • removedInput schema / properties / organizationId / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already carry readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is settled. The description adds genuinely useful behavior beyond that: which fields are omitted from the response and the exactly-one-of scoping requirement. It does not mention pagination or result-size behavior, which keeps it short of a 5.

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?

Two sentences, front-loaded with the core action and scope, followed by the exclusion and the sibling hand-off. No restated name, no filler, and the most decision-relevant constraint (exactly one ID) is embedded rather than buried.

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 3-parameter, read-only list tool with no output schema, the definition covers scope, exclusivity, omitted fields and the alternative route. The only meaningful gap is return volume/pagination behavior, which is a minor omission for a non-destructive list call.

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 the schema already documents logId, organizationId and the state enum with its Open default. The description reinforces the mutual-exclusivity rule but adds nothing about the state filter or ID formats beyond the schema, so the baseline 3 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 description opens with a specific verb plus resource ('List automated recommendations') and narrows the subject matter to error monitoring setup, security and configuration. It also names the sibling that returns the omitted fields, so an agent can distinguish it from recommendations_get_details immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the selection rule explicitly: exactly one of logId or organizationId, and it routes the agent to recommendations_get_details when descriptions or suggestions are needed. The when-to-use-this-vs-alternative decision is fully covered without 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