Skip to main content
Glama

Search Rosuii features

search_features
Read-onlyIdempotent

Search verified public product capabilities in English or Bangla.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_features"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional feature or capability search text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety is covered. The description adds real scope context beyond that: results are restricted to 'verified' and 'public' capabilities, meaning unverified or internal features are excluded. It says nothing about result volume, ranking, or behavior when the query is omitted.

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?

A single front-loaded sentence with no filler and no repetition of the name or annotations. It is efficient, though the brevity edges into under-specification rather than tight completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

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

For a one-parameter, read-only lookup with full annotation coverage and no output schema, the description is close to adequate. The notable gap is that the parameter is optional, and the description never says what happens with an empty query (list everything vs. error), which an agent needs before calling it with no arguments.

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 coverage is 100% and there is only one optional string parameter, so the schema already carries the burden; baseline 3 applies. The description does add meaning the schema lacks, namely that the query may be expressed in English or Bangla. It does not clarify what an omitted query means, which is the one semantically important open question.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Search') and a specific resource ('verified public product capabilities'), plus a language scope. An agent can tell this is a free-text lookup over feature data, though it does not explicitly distinguish itself from the sibling get_feature, which presumably retrieves a single known feature.

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

Usage Guidelines2/5

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

No when-to-use, when-not-to-use, or alternative is named. The agent must infer that this is the tool for discovering features when it does not already have an identifier, and infer that get_feature is the alternative once one is known. The English/Bangla note hints at input expectations but is not routing guidance.

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