Skip to main content
Glama
Sign In

Site Pack

by io.github.Nero-Engine
OverviewDiscussionsAdmin

What Site Pack can do

list_capabilities
Read-onlyIdempotent

Lists Site Pack's tools, the date its rules were last checked, what it covers (nations, project types, work 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.3/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, read-only, closed-world operation. The description adds meaningful behavioral context beyond them: it enumerates the returned content (tools, rules last-checked date, coverage, deliberate exclusions) and notes it is free and takes no input. A 4 rather than 5 because it does not describe response shape or format.

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 tight sentence that front-loads the action and enumerates the value returned. No filler or repetition.

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

Completeness5/5

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

For a zero-parameter discovery tool, the description covers purpose, cost, input requirements, and the information returned. With annotations carrying the safety profile, nothing critical is missing.

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?

There are zero parameters, so the schema imposes no semantic burden; baseline is 4. The description correctly notes 'needs no input', reinforcing the empty schema.

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 the exact resource ('Site Pack's tools') plus the metadata returned (last-checked date, coverage, exclusions). This is clearly a meta/capability tool, distinguishable from the domain-specific siblings without opening the schema.

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?

Provides context ('Free, needs no input') but never explicitly says when to call it versus a domain sibling or that it should be called first. The usage is inferable from it being a capability listing, but the definition lacks explicit routing guidance.

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

All Site 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