Skip to main content
Glama
mcp-server-starter

mcp-server-starter

by humzagk

Search Example Help Centre

search_items
Read-only

Search Example Help Centre articles using keywords or natural-language questions. Returns relevant matches with short snippets; call get_item for full article text.

Instructions

Search help-centre articles in Example Help Centre. Returns the best matches with a short snippet; call get_item for the full text.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (1-25)
queryYesKeywords or a natural-language question

Output Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is settled. The description adds genuine behavioral context beyond that: results are ranked best matches and contain only a short snippet, which explains why a follow-up get_item call is needed.

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, zero filler, with the search purpose front-loaded and the follow-up action trailing. Every clause carries information an agent needs.

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 two-parameter read-only search with full schema coverage and an output schema, the description covers purpose, result shape, and the follow-up path. The only minor gap is any hint about result volume or when to widen/narrow the query, which is not strictly required here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so query ('keywords or a natural-language question') and limit ('1-25') are already fully documented. The description adds no syntax, query-operator, or limit guidance, so the baseline 3 applies.

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 and resource ('Search help-centre articles in Example Help Centre') and explicitly positions the sibling: use get_item for full text. An agent can distinguish search from retrieve without opening either schema.

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?

Gives a clear routing rule to the alternative tool ('call get_item for the full text'), which is exactly the decision an agent faces after a search result. It stops short of exclusions (e.g., when not to search at all), but the primary fork is covered.

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