Get free service capabilities, limits, privacy and connection details; does not scan a target.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing a safe read-only operation. The description adds behavioral context by specifying 'does not scan a target', which clarifies it performs no target interaction. This goes beyond the annotations by describing what the tool does not do, adding value without contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that front-loads the main purpose and includes a key distinction ('does not scan a target'). Every word contributes to clarity, with no redundant or filler content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has no parameters and an output schema exists, so return format is covered. The description explains the core functionality and a key boundary (no scanning). However, it does not explicitly mention sibling tools or provide guidance on when to choose this over get_selection_report or scan_mcp_metadata, leaving some contextual gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero parameters, so schema coverage is 100%. With no parameters to document, the description does not need to provide parameter details. The baseline for zero parameters is 4, and the description adds no unnecessary param info, so this score is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'Get' and clearly states the resource: 'free service capabilities, limits, privacy and connection details'. It also distinguishes itself from sibling tools by explicitly saying 'does not scan a target', which differentiates it from scan_mcp_metadata. This gives the agent a precise understanding of the tool's function.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use this tool: when you need service information, not scanning. The phrase 'does not scan a target' provides a negative condition but does not explicitly name alternative tools or state when to use them. It offers clear context but lacks explicit exclusions or alternative routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a distinct function: scanning new targets, retrieving existing reports, and providing service info. No overlap in purpose, and descriptions clearly differentiate them.
Two tools follow the verb_noun pattern (get_, scan_), but the third is a noun-only name (selection_lab_info), creating a minor inconsistency. Still, all are snake_case and readable.
With only 3 tools, the server is tightly scoped to its core purpose: scanning and retrieving reports. Each tool is necessary and no redundant tools exist.
The server covers the full lifecycle: scan to create a report, retrieve it by id, and get service information. There are no obvious missing operations for this narrow domain.