Skip to main content
Glama
Sign In
mcp-sumologic

mcp-sumologic

by giftHEALTH
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_sources

Retrieves the list of sources configured for a specified Sumo Logic collector using its collector ID.

Instructions

List sources for a Sumo Logic collector.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "collectorId": "<collectorId>"
    },
    "name": "list_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
collectorIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations exist, so the description carries full burden. However, it does not disclose behavior like pagination, error handling, or what happens if the collector ID is invalid. Only a basic listing action is implied.

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

Conciseness2/5

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

The description is extremely short (one sentence), but it is under-specified. While short, it sacrifices necessary detail, making it less effective. Not optimally front-loaded with critical information.

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

Completeness1/5

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

Given the absence of output schema, no annotations, and 3 parameters (1 required), the description is severely lacking. It fails to describe return values, pagination behavior, or any preconditions, making it inadequate for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description does not elaborate on any parameters (collectorId, limit, offset). It provides no semantic meaning beyond the raw schema, failing to compensate for the coverage gap.

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 clearly states the verb 'List' and the resource 'sources for a Sumo Logic collector'. It distinguishes from sibling tools like 'list_collectors' and 'get_collector' by targeting a specific child resource.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., if only collector ID is known, or to get sources for a specific collector). No when-not-to-use or context is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools