Skip to main content
Glama
Sign In
Pagerlane MCP Connector

Pagerlane MCP Connector

by si-essence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

keep_list_applications

Read-only

Lists topology applications from the Keep API so you can see all monitored services and their identifiers. Use it to inspect available applications before querying alerts, incidents, or dependencies.

Instructions

List topology applications. GET /topology/applications.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the description. The description adds only the raw endpoint path 'GET /topology/applications' and says nothing about result volume, pagination, or what an application record contains, which is thin added value.

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 short sentences, front-loaded with the purpose before the endpoint reference, with no filler. The size is appropriate for a parameterless list tool, though the endpoint sentence borders on redundant restatement.

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?

For a simple zero-parameter read tool with annotations and no output schema, the description covers the minimum needed to invoke it. It still omits the domain meaning of 'applications' and whether results are filtered or scoped to the caller's tenant, which an agent would want before calling.

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, so there is no parameter semantics for the description to explain. Baseline 4 applies; the description is not expected to compensate for a schema that has nothing to describe.

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 ('List topology applications'), which separates it from the singular keep_get_topology sibling. However, it never explains what a 'topology application' actually is, so an agent unfamiliar with the domain still has ambiguity about the returned entity.

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?

There is no when-to-use guidance, no mention of alternatives such as keep_get_topology or keep_list_workflows, and no stated preconditions. The agent must infer that this is the enumeration counterpart of the topology getter purely from the tool name.

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