Skip to main content
Glama

Search the help center

search_help_articles
Read-onlyIdempotent

Searches the Enrichment.kids help center for how something works, returning up to five articles with a one-sentence summary and each article's public address. get_help_article reads one in full.

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": {
      "question": "<question>"
    },
    "name": "search_help_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYesWhat the person wants to know, in a few words: 100 characters at most.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / question / description
      Previous value: -"What the person wants to know, in a few words."New value: +"What the person wants to know, in a few words: 100 characters at most."
    • changedInput schema / properties / question / maxLength
      Previous value: -200New value: +100
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the description's job is to add context beyond that. It does so by disclosing the result cap ('up to five articles') and the shape of each result (one-sentence summary plus public address), which matters for deciding whether to follow up with get_help_article.

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 zero filler: the capability and its return shape come first, and the routing hint to get_help_article follows. 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.

Completeness5/5

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

There is no output schema, so the description must describe return values itself, and it does: count limit, per-article summary, and address. Combined with the annotations covering safety and the fully documented single parameter, nothing an agent needs to call this correctly is missing.

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?

With a single parameter at 100% schema coverage, the schema already documents the 'question' field including its 100-character limit. The description's phrasing 'for how something works' lightly frames the input as a natural-language question but adds no syntax or formatting guidance beyond the schema, so the baseline of 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 ('Searches the Enrichment.kids help center') plus the intent it serves ('for how something works'). It explicitly contrasts with the sibling get_help_article, which reads one article in full, so an agent can distinguish the two 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 clear context for use (finding how something works) and names the natural follow-up alternative, get_help_article, for full text. It does not state exclusions or preconditions, such as what to do when no articles match, but the search-then-read flow is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources