Skip to main content
Glama
Sign In

Ridge Pack

by io.github.Nero-Engine
OverviewDiscussionsAdmin

What Ridge Pack can do

list_capabilities
Read-onlyIdempotent

Lists Ridge Pack's tools, what it covers (nations, roof shapes, coverings, job types) and what it deliberately does not do. Free, needs no input.

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_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds information the annotations do not: that the response enumerates the toolset, the domains covered, and the deliberate boundaries, and that the call is free. It does not say how the result is structured, but with no output schema that is a modest gap.

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 short sentences with no filler, and the core purpose is front-loaded ahead of the scope and cost details. Every clause carries information an agent would otherwise have to guess.

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 no-input discovery tool with rich annotations, the description covers what it returns (tool list, coverage domains, exclusions) and its cost. Only the shape of the response is left implicit, which is a minor omission given the tool's simplicity.

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-parameter tool, so the baseline is 4; the description confirms that with 'needs no input', removing any doubt about whether arguments are expected. No further parameter meaning is needed.

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?

States a specific verb ('Lists') and resource ('Ridge Pack's tools') and then scopes the content precisely: coverage of nations, roof shapes, coverings, and job types, plus deliberate exclusions. This is clearly a meta/discovery tool and cannot be confused with the task-specific siblings such as roof_takeoff or check_building_regs.

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

Usage Guidelines4/5

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

'Free, needs no input' gives a clear cost/effort signal that makes this the cheap first call to orient before invoking a task tool, and the stated exclusions tell an agent when this tool will not answer a domain question. It stops short of an explicit 'call this first when unsure which tool to use' instruction or naming an alternative, so it is strong context rather than a full when/when-not rule.

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

All Ridge Pack toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources