Skip to main content
Glama
wiz0floyd

best-practices-mcp

by wiz0floyd

Search mynow.servicenow.com

servicenow_search

Search ServiceNow's public best-practices library across Knowledge, Best Practices, and Developer Portal docs without authentication. Automatically detects content type from query or allows explicit filter.

Instructions

Search ServiceNow's public best-practices library (mynow.servicenow.com) across Knowledge, Best Practices, Developer Portal docs, and other indexed content. No authentication required. Leave contentType unset to search all sources; use the 'table' field on prior results to discover valid contentType filter values. A natural-language content-type cue in the query itself (e.g. 'stream connect best practices') is detected and routed to that contentType filter automatically, with the cue phrase removed from the search text — see the response's searchedQuery/detectedContentType fields for what was actually searched. Set contentType explicitly to override this detection. contentType filtering only applies to a small fixed raw page, not the full corpus — if that filter would return nothing despite real matches existing (totalResults > 0), the response falls back to unfiltered results and sets contentTypeFilterDegraded/note rather than silently returning empty.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYesSearch term(s)
offsetNo
contentTypeNoOptional table/source filter (e.g. 'kb_knowledge', 'sn_communities_post'). Leave unset to search all sources.
Behavior5/5

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

Discloses no authentication required, automatic content-type detection, routing of query cues, fallback when filter returns nothing, and response fields (searchedQuery, detectedContentType, contentTypeFilterDegraded/note). Fully transparent beyond annotations (none provided).

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?

Single paragraph with front-loaded purpose sentence. Contains useful details but slightly verbose; could be more concise. Still well-structured.

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?

Covers authentication, filter behavior, fallbacks, and partial response structure. Lacks full response details but acceptable for search tool. Paging (offset/limit) not elaborated beyond schema.

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?

Schema coverage is 50% (2/4 parameters described). Description adds meaning: how to discover contentType values, automatic detection, and fallback. Compensates for schema gaps and adds unique semantics.

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?

Clearly states the tool searches ServiceNow's public best-practices library (mynow.servicenow.com) across multiple content types. Distinguishes from sibling tool by specifying search functionality.

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?

Provides guidance on when to set contentType, how to discover valid values, and fallback behavior. Does not explicitly mention alternatives beyond listing content types, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wiz0floyd/best-practices-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server