Skip to main content
Glama

Utility: Fallback Feature Search

find_feature_entry
Read-onlyIdempotent

[Fallback] [What it does] Searches the DSers feature catalog by English intent keywords only after confirming no existing DSers tool can complete the request; returns feature and application-page destinations without performing any business action. [When to use] Call only after verifying every other DSers tool cannot fulfill the request and a page entry point is needed; trigger words: feature entry, where to set up, no tool covers this, navigate to a feature. [When not to use] Do not use for product, order, or store queries that have dedicated tools (e.g. get_order, list_stores); this tool never substitutes for a business action. [How to use] Pass specific English intent keywords as query; at most 10 destinations are returned. An empty matches list is a valid result meaning no fallback destination exists. truncated=true means more matches exist beyond the limit — narrow the keywords or raise limit. [Side effects] Read-only; no data is changed. [Confirmation] No confirmation required. [Follow-up] If a match fits, explain the destination and ask whether to open its URL; if none fits, report there is no suitable destination and stop.

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": "find_feature_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum fallback destinations returned (default 5, max 10).
queryYesSpecific English keywords describing the DSers capability that is unavailable through existing MCP Tools.

Output Schema

NameRequiredDescriptionDefault
matchesYesRelevant DSers page destinations ordered by match quality
truncatedYesWhether additional matches exist beyond the result limit
catalog_countYesTotal feature records searched
matched_countYesRelevant records found before applying the result limit
returned_countYesRecords returned after applying the result limit
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, but the description adds real context beyond them: no business action is ever taken, an empty matches list is a valid result, truncated=true signals more matches exist, and no confirmation is required. The follow-up guidance on asking before opening a URL is a useful operational constraint. It stops short of describing permissions or rate limits, but for a read-only catalog lookup that is minor.

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?

Sectioned headers make it skimmable and the fallback label is front-loaded. The bracketed labels are slightly heavy for the amount of content, but every section carries distinct information, so little is wasted.

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?

Covers purpose, gating condition, parameter intent, result semantics (empty matches, truncation), side effects, and follow-up behavior. With an output schema present and annotations rich, nothing an agent needs in order 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.

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, yet the description adds meaning: query must be specific English intent keywords for a capability unavailable through existing tools, and the 10-destination cap plus the truncated flag explain the interaction between limit and results. This goes beyond the schema's own field text.

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 DSers feature catalog") and immediately pins its role as a fallback that returns destinations "without performing any business action." The agent can distinguish it from every sibling business tool without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use with trigger words ("feature entry, where to set up, no tool covers this, navigate to a feature") and explicit when-not-to-use naming concrete alternatives like get_order and list_stores. The precondition of verifying no other tool can fulfill the request is stated twice, so the routing decision 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.